Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: why no fdopen() in dpANSI C?
Message-ID: <7655@brl-smoke.ARPA>
Date: 11 Apr 88 05:41:46 GMT
References: <302@goofy.megatest.UUCP> <225800017@uxe.cso.uiuc.edu> <8042@elsie.UUCP> <2567@ttrdc.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <2567@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
>Oh, GROAN.  Why not?  Sometims that's the most efficient way of getting a
>stdio stream open onto a file which needs options on open() or creat() other
>than the default, ...

There is no fdopen() in ANSI C because there are no UNIX file
descriptors in ANSI C.

UNIX (POSIX) systems can provide fdopen() as an extension to an ANSI-
conforming C implementation.  Nobody is insisting that it go away,
except it must not appear in <stdio.h> in a pure ANSI C environment
(special implementation-dependent things may be done to enable its
appearance; this issue is still being discussed by the standards
committees).