Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-sem!ron
From: ron@brl-sem.ARPA (Ron Natalie )
Newsgroups: comp.lang.c
Subject: Re: My comments to X3J11 (1000 lines)
Message-ID: <565@brl-sem.ARPA>
Date: Tue, 6-Jan-87 19:54:44 EST
Article-I.D.: brl-sem.565
Posted: Tue Jan  6 19:54:44 1987
Date-Received: Tue, 6-Jan-87 23:52:12 EST
References: <2144@brl-adm.ARPA> <1202@ucbcad.berkeley.edu>
Organization: Electronic Brain Research Lab
Lines: 14

In article <1202@ucbcad.berkeley.edu>, faustus@ucbcad.berkeley.edu (Wayne A. Christopher) writes:
> A lot of people have been worrying about the proliferation of names
> that don't begin with `_' which are pre-defined by the implementation.
> But seriously, we can't expect `read' to be re-defined as `_read' in
> UNIX -- the things that UNIX defines are going to stay defined.  How
> many programmers have had serious problems with conflicts like this?

Easy, UNIX can have "read" in libc (or liba for those running Version
6).  It is just prohibitted that any of the Standard C routines such
as PRINTF use "read."  That way if a user defines his own function
called read, he doesn't break any calls he made to the "Standard Set
of Routines."

-Ron