Date: Sun, 11 Aug 1996 09:56:13 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Grzegorz Nowakowski <krecik AT ii DOT uni DOT wroc DOT pl>
Cc: djgpp AT delorie DOT com
Subject: Re: DJGPP HELP!!!!!
In-Reply-To: <KRECIK.96Aug8105341@ii.uni.wroc.pl>
Message-Id: <Pine.SUN.3.91.960811094724.24678G-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 8 Aug 1996, Grzegorz Nowakowski wrote:

> Is there ANSI C specification available on-line?

ANSI charges quite a lot of money for their spec ($130 I think), so you 
won't find it anywhere for free.  I usually use "The Standard C" by 
Plauger et. al. (Micrsosoft Press) and "The Standard C Library" by 
Plauger as very good replacements.  There is also "Annotated ANSI C" by 
Schildt (sp?), but I never used it.

> Actually, when I
> want to write clean code, the only reference I have is BC 3.1 help
> (which points if such function is in ANSI C or not).  And that's the
> main reason I keep the compilet on my HD. :-(

Are you kidding??  If all you need to know is whether a function is ANSI
or not, look at the DJGPP header file that declares it.  Functions that
are declared after the #ifndef __STRICT_ANSI__ are non-ANSI.  You can test
existing sources by compiling with "gcc -Wall -ansi": those functions
which produce warnings saying they are ``implicitly decalred'' are
non-ANSI.