Re: How to convert Infix notation to postfix notation

In
<f6731d50-9f4d-45c8-b0ea-d7b212b8fc68@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
spinoza1111 wrote:

On Nov 5, 12:47 am, Seebs <usenet-nos...@xxxxxxxxx> wrote:
On 2009-11-04,spinoza1111<spinoza1...@xxxxxxxxx> wrote:

Oh great, so you haven't opened it.

I dunno, my memory's crap. I can't remember which books I've read.

So we listen to your opinions why?

Because he can remember what he's learned from them.

<snip>

I'm not complaining. You are.

Uh, actually, you're complaining. You were claiming that my
behavior didn't meet your needs.

No, your behavior is unacceptable.

To you, perhaps, but not to normal people.

<snip>

I don't recall having made any particular judgements about Navia.
I have enough data to state confidently that you don't know what
you're talking about, as widely demonstrated across several
different (though related) fields of inquiry.

...or that I know so much more, and am so free of learning
disorders, that you can't follow my reasoning.

In your dreams.

and you were out of line with Schildt because you
don't know Microsoft platforms.

First off, several of his claims were false even there.

Secondly, if he wanted to write a book called "C for Microsoft
Platforms Only: The Incomplete Reference With A Few Errors To Make
Sure You Are Staying On Your Toes", I have every confidence that it
would be well-received.

Grow up. Most platforms are Microsoft.

Absolute rubbish. If you're going by installation count, there are
approximately 1,000,000,000 PCs out there, not all of which run MS
operating systems. And there are well over four times as many mobile
phones, of which only a tiny fraction run Windows Mobile. And if
you're going by platform count, Microsoft has written a handful of
versions of Windows (1, 2, 3, 95, 98, NT3.5, NT4, ME, 2000, XP,
Vista, 7, plus slight mods thereof), and they released a few versions
of MS-DOS. There are at least that many different mainframe operating
systems, and then there's all the minicomputer OSs, not forgetting
alternate PC OSs, and all the Mac platforms, various games consoles,
and a whole bundle of mobile phone systems, engine management
systems, set top boxes, and various other embedded devices. MS is a
tiny drop in a rather large puddle.

<snip>

Your inability to grasp this point astounds me. The question is
not one where there's a tradeoff. Covering the far/huge memory
model crap? Perfectly reasonable, because it's going to be useful
to people on a common platform. Note: *It offers them a benefit
they cannot have by doing things the standard way*. Using
uppercase letters for headers specified as lowercase? Stupid,
*because it does not offer any benefit*.

Perhaps distinguishing lower and upper case file names is the
mistake.

No, the mistake is Schildt's *failure* to distinguish between upper
and lower case.

It might seem cool, but it's English - centric.

Hardly. A great many languages use case distinctions just as much as
English does, and in some csaes even more (e.g. German).

<snip>

What is worse,
you enabled a series of personal attacks because you only
published 20 flaws, but made references to hundreds, which you
have not, as far as I can see, documented.

So what? Plenty of other people have pointed out flaws, and there
are plenty more. A representative sample is more useful.

No, they haven't. They've repeated what you have said, or they have
said that "Schildt sucks", which isn't pointing out a flaw at all.

Wrong. I have pointed out flaws that have reported by neither Seebach
nor Feather.

I have plenty of consideration for others, but unlike a feminized
corporate dweeb "this animal defends itself when attacked".

So does my cat, albeit more effectively.

Corporatese? I don't think so.
I do.

Of course you do. But you can't actually, say, justify or support
that point.

I have supported it.

No, you've just ranted about it. "Support" means reference to
independently verifiable and /relevant/ facts that give credence to
your case.

It is corporate-speak to pass on rumors about a person's competence
without substantiation, and this is what you've done with Schlidt.

Wrong. He has substantiated the claim.

<snip>

Even if we grant (despite the lack of support or evidence from you)
the theoretical notion that C is a source of errors, it's still
noticeable that those errors are exacerbated by people trying to
learn from Schildt, and mitigated by people trying to learn from
other authors.

That's simply not the case.

Er, yes it is.

As it happens, people use his approaches to generate correct
software.

If they follow his advice, they can hardly fail to produce incorrect
software.

What part of "critical thinking" and "testing" don't you understand?

He has thunk critically. He has tested. He has reached conclusions. He
has produced a report to promulgate those conclusions. That you do
not agree with the conclusions would be interesting if you knew C.

No ***, *** Tracy. Have you ever heard about the use of white
space in technical writing?

Yes.

Keep in mind, unless you've got more books out there, I've done 2-5
times as much technical writing as you have. White space? A good
thing *used

Wow, the autistic writer of documents nobody bothers to read.

Unless you can support that claim with independent evidence of a 0
readership (which you can't), it would be proper to conclude that the
claim is nonsense.

intelligently*. Double-spacing paragraph text would not be a good
thing. Large spaces between members of lists, also not good.

Corporatese, because a naming standard doesn't work or fail. It
is usable or otherwise.

A naming standard presumably has goals. The goals given for
Hungarian notation are not met by Systems Hungarian. Therefore, it
does not work.

In my experience this is not the case.

If you had any useful experience you'd know otherwise.

Systems Hungarian makes
selection of data type a design point and not coding and the fact
that it's difficult to change is a good thing. This is because
before coding starts you need to know your data types.

No, a good design is independent of such language-dependent details as
data types. For numeric values it needs to specify ranges, but that's
all. The choice of type is the province of the programmer, not the
designer.

<snip>

If you're a technical writer, what are you doing misrepresenting
yourself as a competent programmer?

Your racism doesn't stop you being homophobic, does it? Likewise, his
programming doesn't stop him being a technical writer.

<big ol' snip on EGN's behalf because he's either too lazy or too
stupid to do it himself>

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
"Usenet is a strange place" - dmr 29 July 1999
Sig line vacant - apply within
.

Quantcast