From:	eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Question about ISO C99 and GCC
Date:	7 Sep 2002 12:54:00 GMT
Organization:	Ericsson Erisoft AB, Sweden
Lines:	27
Message-ID:	<alcst8$dbk$2@antares.lu.erisoft.se>
References:	<3d71a27d DOT 23705885 AT news DOT nzwide DOT ihug DOT co DOT nz> <3d794cbc DOT 170442372 AT news DOT concentric DOT net> <200209070110 DOT g871AiW02735 AT envy DOT delorie DOT com> <3d7970de DOT 179693669 AT news DOT concentric DOT net>
NNTP-Posting-Host:	lws256.lu.erisoft.se
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

James Haley (haleyjd AT NOSPAM DOT hotmail DOT com) wrote:
: So, now that I better understand the source of this requirement, I
: have one question.  Is it the position of the GCC guys that all code
: to be compiled under GCC should be ISO C99 compliant? I was totally
: unaware of the addition of the new requirement in this standard, as
: I'm sure you ascertained.

Again, this is the DJGPP list/newsgroup. You need to ask this on the
gcc list/newsgroup.

(But AFAIK GCC is aiming for C99 compliance, so I guess the answer is
yes.)

: If this is the case, then it'll be much easier for me now to make sure
: all my source is ISO C99 compliant rather than being revisionist and
: fixing one issue at a time when it arises :->

Yes, that should do it. But beware that there are new functions in C99
that DJGPP libc doesn't implement yet. We need volunteers for that.

I'm also unsure if the current release DJGPP headers really are C99
compliant.


Right,

						MartinS

- Raw text -