Mail Archives: djgpp/1996/08/12/11:58:00
At 09:56 11/08/96 +0200, Eli Zaretskii wrote:
>
>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. :-(
>
Another good source on writing "clean C" is the book "C A Reference Manual"
by S. P. Harbison and G. L. Steele jr., PH, 4th ed., 1995, ISBN
0-13-326224-3. In addition to cover the ISO standard including 1994
ammendments, it has an interesting definition of "clean C" which includes
the possibility of compiling a plain C source to be compiled as C++ w/o
generating errors/warning. IMHO it is a good reference to have available!
>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.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cesar Scarpini Rabak E-mail: csrabak AT ipt DOT br
DME/ASC Phone: 55-11-268-35221Ext.350
IPT - Instituto de Pesquisas Tecnologicas Fax: 55-11-268-5996
Av. Prof. Almeida Prado, 532. Sao Paulo - SP 05508-901 BRAZIL
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Raw text -