Re: help w/ c/c++ problem

On Thu, 05 Jul 2007 14:23:44 -0700, in comp.lang.c , Keith Thompson
<kst-u@xxxxxxx> wrote:

This has nothing to do with whether anyone else was right or wrong, or
with what anybody admits. It's a simple technical point.

I don't propose to discuss this any further after this, but I need to
clarify the above, since you've seen fit to complain about it.

About four years ago, I argued strongly FOR precisely the
interpretation that is currently put on the words "or in some other
implementation defined manner". I was however shouted down by several
experts, who made strong arguments against my PoV. I accepted their
apparently greater wisdom.

So you will understand that I'm amused yet annoyed to see at least
some of the same experts now arguing the other side of the coin, and
even more entertained to see them vigorously attacking my posts.

Thus your statement that
The C Standard REQUIRES main to return an int.
is incorrect. A conforming implementation may allow 'void main(void)'
-- or 'long double main(unsigned long long foobar)'.

<uberpedant>
you too are incorrect since you need to add the words "provided it
documents the alternate form".
</>
If I had inserted the word "portable" somewhere there, would that have
satisfied by the way?

What's so difficult about that?

See my response elsethread, which you've either ignored, or missed.

I also want to point out that the uber-pedantry with which this point
has been debated has almost certainly given some newbies the mistaken
impression that void main() is generally ok. I trust those of you who
leapt upon this particular hobbyhorse feel happy with that.

EOT.
--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan
.

Relevant Pages

  • Re: help w/ c/c++ problem
    ... The C Standard REQUIRES main to return an int. ... A conforming implementation may allow 'void ... you too are incorrect since you need to add the words "provided it ...
    (comp.lang.c)
  • Re: why is casting malloc a bad thing?
    ... >> But its impossible for it to be incorrect. ... I suspect Mark thought you were claiming that a void * ...
    (comp.lang.c)
  • Re: Copy Constructors and Assignment Operator, When should I use?
    ... the erased element, so the above is incorrect. ... void removeFstItem{ ... vecItr!= m_vecB.end; ...
    (microsoft.public.vc.language)
  • Re: Memory allocation for an initialized character pointer;
    ... But, speaking strictly in regard to the standard, we can say it is ... Where does the Standard explicitly say that void mainis ... a strictly conforming program can't rely on the order of bit- ... In C89, it's incorrect. ...
    (comp.lang.c)
  • Re: lvalue rvalue discussion
    ... I'm sorry, that's incorrect. ... 'void' is one of the fundamental types in C++, ... Vladimir Grigoriev: ... Constructors are declared sans result type, not even void. ...
    (microsoft.public.vc.language)