Date:	Tue, 22 Nov 94 19:08:06 -0500
From:	dj AT stealth DOT ctron DOT com (DJ Delorie)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	ansi/posix results

Thanks for all the feedback.  Here's what I've decided, based on it:

* When you say you're an ansi program, or a posix program
(_POSIX_SOURCE), you will only get the prototypes and defines that
ansi/posix say you are required to have available to you.

* Internally, libc will use the __ff functions when an ansi function
calls a posix function, or when either call a non-posix function, so
that the application may redefine those without messing up libc.a.

* The headers will prototype the __ff functions in the "I want
everything" section.

* functions that are not posix, but aren't __ff, will not be allowed
in posix headers, unless I absolutely can't avoid it.  When in doubt,
I will choose the same header that Borland 3.0 uses, since that's what
I've got available.

DJ

- Raw text -