Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.lang.c
Subject: What's basis for draft C Standard Rationale reserved identifier claim?
Message-ID: <7428@elsie.UUCP>
Date: Fri, 29-May-87 10:55:58 EDT
Article-I.D.: elsie.7428
Posted: Fri May 29 10:55:58 1987
Date-Received: Sun, 31-May-87 06:37:53 EDT
Organization: NIH-LEC, Bethesda, MD
Lines: 23

Page 64 of the draft C Standard's Rationale document reads (in part):

	. . .all external identifiers defined by the library are reserved
	[for the implementor]. . .Also reserved for the implementor are *all*
	external identifiers beginning with an underscore, and all other
	identifiers beginning with an underscore followed by a capital letter
	or an underscore. . .With these exceptions, the Standard assures the
	programmer that *all other* identifiers are available, with no fear of
	unexpected collisions when moving programs from one implementation to
	another.

Now I've been able to find the place in the Standard itself where "all external
identifiers defined by the library are reserved."  And I've been able to find
the place where identifiers beginning with an underscore are reserved.  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.

I'd appreciate it if someone would quote the part of the Standard that provides
the assurance.
-- 
	UUCP: ..seismo!elsie!ado	   ARPA: elsie!ado@seismo.CSS.GOV
	     Elsie and Ado are trademarks of Borden, Inc. and Ampex.