🚀 go-pugleaf

In article <1992Apr9.165859.18578@wam.umd.edu> krc@wam.umd.edu (Kevin R. Coombes) writes:
> I have a question about the ANSI C header stdlib.h. A certain compiler that
> shall for the moment remain nameless includes macros for min(a,b) and 
> max(a,b) in <stdlib.h>.

In article <1992Apr10.162327.29202@borland.com>, pete@borland.com (Pete Becker) writes:
> 	If you compile in ANSI mode (with the -A switch), min and max go
> away.  They also go away when compiling C++.
> 	-- Pete

Turbo C 2.01 does have problems in its <stdlib.h> which the -A option does
not fix.  Example:

	int boo[2];
	#define state 0[boo]
	#define seed  1[boo]
	#include <stdlib.h>
	...

I hadn't noticed this before today, because I hadn't used tcc before today.
It turns out that most of the functions defined in stdlib.h have identiers
in their prototypes, and those identifiers are in the user's name space.

Then of course there's <assert.h>, with Borland's manual explicitly
saying that assert "turns into an if statement".

Where are the *standard* C compilers?  (Ok, I know about Norcroft, but
last I heard they didn't have a compiler for PCs or Encore Multimaxes.)

I spent several hours last week writing a <stdio.h> for Gcc on an
Encore Multimax; not having one it picked up the /usr/include/stdio.h,
and in strict ANSI mode it didn't #define n16, so the record structure
for a stream control block was wrong.  Result: happy compiler, insane
program.  Where are the *standard* C compilers?

-- 
I am writing a book on debugging aimed at 1st & 2nd year CS students using
C/Modula/Pascal-like languages.  Please send suggestions (other than "you
_must_ cite "C Traps and Pitfalls") to ok@goanna.cs.rmit.oz.au