Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!faustus
From: faustus@ucbcad.berkeley.edu (Wayne A. Christopher)
Newsgroups: comp.lang.c
Subject: Re: My comments to X3J11 (1000 lines)
Message-ID: <1202@ucbcad.berkeley.edu>
Date: Tue, 6-Jan-87 14:58:07 EST
Article-I.D.: ucbcad.1202
Posted: Tue Jan  6 14:58:07 1987
Date-Received: Tue, 6-Jan-87 23:20:00 EST
References: <2144@brl-adm.ARPA>
Organization: CAD Group, U.C. Berkeley
Lines: 13

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?
The problem of non-standard identifiers in libraries isn't a problem at
all, as I pointed out in a previous message (just make sure other
library routines use "hidden" variations), and macros defined in header
files usually will cause an error, so at least bugs aren't going to
remain hidden because of this.  Before we spend too much time fixing
problems, let's make sure that they're problems in the first place.

	Wayne