Re: How to convert Infix notation to postfix notation
- From: Richard Heathfield <rjh@xxxxxxxxxxxxxxx>
- Date: Sun, 08 Nov 2009 05:38:26 +0000
In <_t-dnW_AFbznyGvXnZ2dnUVZ8oGdnZ2d@xxxxxx>, Richard Heathfield
wrote:
In
<28888455-ec8d-4e62-b204-05af74369ca4@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
spinoza1111 wrote:
<snip>
Here, you made a wild and unfounded charge about the Microsoft
development environment,
Rubbish. He's just suggesting that you might not know how to drive
it. And it's clear that he's right - you don't.
Look, I'll tell you what, I'll just post this, and then... watch
this space...
Okay, I found a relatively recent version of the code, and compiled it
using a Microsoft compiler. Here's what it had to say:
nilges.c(1) : warning C4001: nonstandard extension 'single line
comment' was used
nilges.c(68) : error C2001: newline in constant
nilges.c(69) : error C2143: syntax error : missing '{' before '-'
nilges.c(69) : error C2059: syntax error : '-'
nilges.c(69) : error C2001: newline in constant
nilges.c(160) : warning C4033: 'main' must return a value
nilges.c(164) : warning C4033: 'main' must return a value
nilges.c(195) : warning C4127: conditional expression is constant
nilges.c(278) : warning C4127: conditional expression is constant
nilges.c(571) : error C2001: newline in constant
nilges.c(572) : error C2143: syntax error : missing ')' before
'constant'
nilges.c(572) : error C2198: 'testCase' : too few actual parameters
nilges.c(572) : error C2001: newline in constant
But wait! The linewrap problem only occurs over Usenet, so the source
that Nilges is compiling doesn't have that problem. So let's fix the
linewrap and see what we get:
nilges.c(1) : warning C4001: nonstandard extension 'single line
comment' was used
nilges.c(160) : warning C4033: 'main' must return a value
nilges.c(164) : warning C4033: 'main' must return a value
nilges.c(195) : warning C4127: conditional expression is constant
nilges.c(278) : warning C4127: conditional expression is constant
Well, it's not as informative as gcc, but it is quite clear to me that
his code does not compile cleanly even on the tools he's using when
invoked properly.
--
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
.
- References:
- Re: How to convert Infix notation to postfix notation
- From: spinoza1111
- Re: How to convert Infix notation to postfix notation
- From: Ben Pfaff
- Re: How to convert Infix notation to postfix notation
- From: Seebs
- Re: How to convert Infix notation to postfix notation
- From: Kenny McCormack
- Re: How to convert Infix notation to postfix notation
- From: spinoza1111
- Re: How to convert Infix notation to postfix notation
- From: Richard Heathfield
- Re: How to convert Infix notation to postfix notation
- From: spinoza1111
- Re: How to convert Infix notation to postfix notation
- From: Seebs
- Re: How to convert Infix notation to postfix notation
- From: spinoza1111
- Re: How to convert Infix notation to postfix notation
- From: Nick Keighley
- Re: How to convert Infix notation to postfix notation
- From: Richard Heathfield
- Re: How to convert Infix notation to postfix notation
- From: Seebs
- Re: How to convert Infix notation to postfix notation
- From: spinoza1111
- Re: How to convert Infix notation to postfix notation
- From: Richard Heathfield
- Re: How to convert Infix notation to postfix notation
- Prev by Date: Re: Encoding Return Address and Stack Pointer
- Next by Date: Re: How to convert Infix notation to postfix notation
- Previous by thread: Re: How to convert Infix notation to postfix notation
- Next by thread: Re: How to convert Infix notation to postfix notation
- Index(es):
Relevant Pages
|