Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: _read()
Message-ID: <5493@brl-smoke.ARPA>
Date: Wed, 7-Jan-87 16:24:04 EST
Article-I.D.: brl-smok.5493
Posted: Wed Jan  7 16:24:04 1987
Date-Received: Thu, 8-Jan-87 21:37:28 EST
References: <2144@brl-adm.ARPA> <1202@ucbcad.berkeley.edu> <565@brl-sem.ARPA>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <565@brl-sem.ARPA> ron@brl-sem.ARPA (Ron Natalie ) writes:
>... It is just prohibitted that any of the Standard C routines such
>as PRINTF use "read." ...

Thanks to Ron for pointing this out.  The implication is that
the stdio etc. routines would have to call _read() but the UNIX
user still gets his read() routine from the library.  Thus an
implementation CAN have non-standard non-_* names in the library
after all, so long as they are essentially an orthogonal
extension to the standard-conforming part of the library.