> > But you advised using __P for declarations for the sake of old
> > compilers.  If you're writing prototype definitions, there's no reason
> > to be generous to old compilers in the declarations, since the code
> > won't build on a pre-prototype compiler anyway.
> 
> use __P in *public* header files. (e.g, in <stdlib.h>). it doesn't
> matter for private stuff.

I've used more than 1 compiler that the __P() stuff _doesn't_ work the
way one wants it to (the ansi-std doesn't guarantee that it will).  It
works with gcc, and it works with non-ansi.  If it doesn't work with
your ansi compiler you lose the benefits of prototypes becuase you have
to turn them off.

I'm with Chris D. here, ansi-c has been around for more than a decade at 
this point, lets drop the old compat hacks.

Chris.