Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!cullvax!drw
From: drw@cullvax.UUCP (Dale Worley)
Newsgroups: comp.lang.c
Subject: What's basis for draft C Standard Rationale reserved identifier claim?
Message-ID: <1240@cullvax.UUCP>
Date: Wed, 3-Jun-87 15:27:12 EDT
Article-I.D.: cullvax.1240
Posted: Wed Jun  3 15:27:12 1987
Date-Received: Sun, 7-Jun-87 01:32:50 EDT
Organization: Cullinet Software, Westwood, MA, USA
Lines: 20

ado@elsie.UUCP (Arthur David Olson) writes:
> But I've
> been unable to find the place in the Standard that assures that all other
> identifiers are available to the application programmer with no fear of
> unexpected collisions.

Probably this is stated "negatively", i.e., the general rules for
using identifiers leads you to believe that "all other" identifiers
work, and there is no special rule to tell you that the might not.
Ergo, they work.  (Many standards have an "escape clause" somewhere
that says that the implementation can reserve any external identifiers
it wants.  (I think.))

Dale

-- 
Dale Worley		Cullinet Software
UUCP: ...!seismo!harvard!mit-eddie!cullvax!drw
ARPA: cullvax!drw@eddie.mit.edu
Un*x (a generic name for a class of OS's) != Unix (AT&T's brand of such)