[comp.std.unix] Where can I get POSIX function prototypes?

rfg@PARIS.ICS.UCI.EDU (Ron Guilmette) (02/01/90)

[ This came in with Newsgroups: comp.std.unix,comp.std.c
but I've recently made a policy of not cross-posting discussions,
so I'm putting it only in comp.std.unix.  -mod ]

From: Ron Guilmette <rfg@PARIS.ICS.UCI.EDU>

(I hope that you will all excuse my (nearly total) ignorance of current
standards efforts.)

As part of my work on my "protoize" tool, I need to obtain complete sets
of function prototypes for the library functions available on various
UNIX systems.

Rather than use a multitude of various sets of prototypes (each of which
may be "correct" only for one specific individual implementation of UNIX)
it seems that the sensible thing to do would be to use one single POSIX set
of library function prototypes.  I'd like to do that, but the problem is
that I need to obtain such a set (on-line) somewhere, and I don't know
where to begin.  Can anyone point me at a set of (on-line) POSIX library
function prototypes?  (I certainly don't want to type them all in by hand
from POSIX documents!)

Of course I will ultimately have to augment the POSIX prototypes set with
additional prototypes for specific systems, but for the "core" functions
(i.e. the ones which are covered by POSIX) I'd like my prototypes to reflect
what POSIX is doing rather that reflecting any machine-specific local
variations.

// rfg

Volume-Number: Volume 18, Number 35

donn@hpfcrn.hp.com (Donn Terry) (02/04/90)

From: Donn Terry <donn@hpfcrn.hp.com>

>From: Ron Guilmette <rfg@PARIS.ICS.UCI.EDU>

>Of course I will ultimately have to augment the POSIX prototypes set with
>additional prototypes for specific systems, but for the "core" functions
>(i.e. the ones which are covered by POSIX) I'd like my prototypes to reflect
>what POSIX is doing rather that reflecting any machine-specific local
>variations.

1003.1a is stated in terms of proper prototypes.  It will be available
when balloting completes.  You should be able to get a copy thru
the IEEE CS office, but it isn't current, as the balloting has been
rather hectic of late.  If you're desperate, write.  (donn@hpfcla.hp.com)

Donn Terry  (as an individual)

Volume-Number: Volume 18, Number 41