Xref: utzoo comp.lang.c:6839 comp.unix.questions:5289
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!gorodish!guy
From: guy@gorodish.Sun.COM (Guy Harris)
Newsgroups: comp.lang.c,comp.unix.questions
Subject: Re: Fate of fdopen(3S)??
Message-ID: <39764@sun.uucp>
Date: 22 Jan 88 23:22:54 GMT
References: <2091@pdn.UUCP>
Sender: news@sun.uucp
Lines: 18
Keywords: Draft ANSI C Std, POSIX

>      The rational for leaving fdopen(2S) out of the Draft ANSI C Standard 
> is quite reasonable.  However, how will POSIX handle this function?  Will
> POSIX address those UNIX-specific library subroutines that fall out of
> the Draft ANSI C Standard?

Yes.  See section 8 of Draft 12 of the POSIX standard, C Language Library,
which includes what you might consider routines that aren't in ANSI C and don't
belong there but are "related" to routines that are in ANSI C.  This section
includes "fileno" and "fdopen".

> How will the merged AT&T/Sun effort handle this?

The same way every other UNIX implementation handles it: provide "fdopen",
since the source is already there in SunOS and S5 (and S3 and V7 and 4BSD
and...).
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com