From: nxk3 AT dante DOT student DOT cwru DOT edu (Natarajan Krishnaswami)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problems with pgcc
Date: 25 May 1997 15:34:03 GMT
Organization: Case Western Reserve University, Cleveland OH (USA)
Lines: 29
Message-ID: <slrn5ogmv9.i34.nxk3@dante.student.cwru.edu>
References: <199705241659 DOT AA075583151 AT typhoon DOT rose DOT hp DOT com>    <5m7fh4$qc5$1 AT bore DOT news DOT pipex DOT net> <33886e43 DOT 1786516 AT news> <5m9e2b$9qh$1 AT bore DOT news DOT pipex DOT net>
Reply-To: nxk3 AT po DOT cwru DOT edu
NNTP-Posting-Host: dante.student.cwru.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On 25 May 1997 13:15:55 GMT, nikki <nikki AT gameboutique DOT co> wrote:
> > because in standard C, main MUST return int!
               ^^^^^^^^
> why pray? 

Because that is what the standard says. :)

> void main() has always worked before. works fine under gcc, cc and
> every other c compiler i've ever touched. what's with the '*must*
> return an int' stuff?

He said in _standard_ c it must do so.  That many compilers implement
nonstandard extensions (in this case to support legacy code) does not
make them standard.  For example, many compilers support // as a
comment in C.  While this will certainly be a part of the next
standard (C9X), /**/ is currently the only way to specify a comment,
according to the existing standard[s].

I believe someone posted the relevant section of the standard a short
while ago.


N.
-==(UDIC)==-
"For once I myself saw with my own eyes the Sybil at Cumae hanging
in a cage, and when the boys said to her, 'Sybil, what do you want?'
she replied, 'I want to die.'"

					- From the _Satyricon_ by Petronius