Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.lang.c Subject: Re: $1 check for first person who convinces me main can't be reserved Message-ID: <7402@brl-smoke.ARPA> Date: 2 Mar 88 18:48:09 GMT References: <8016@elsie.UUCP> <8020@elsie.UUCP> <7352@brl-smoke.ARPA> <2801@haddock.ISC.COM> <8025@elsie.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 17 In article <8025@elsie.UUCP> ado@elsie.UUCP (Arthur David Olson) writes: >Nope. Recent drafts say that application programmers aren't allowed to use >__* and _[A-Z]* identifiers, which are reserved to implementers; recent drafts >do not say that implementers may reserve *only* those identifiers. The draft does not specify "programmers" or "implementers", just what identifiers are reserved, period. (4.1.2) Conforming implementations are prohibited from usurping other identifiers via any of the standard headers, and conforming programs cannot defined one of the reserved identifiers. A possible deduction that could be drawn from the rules is that for the most part, _-names are available for the implementation. I think the only real issue is that a keyword is not an identifier, so there is a possible loophole that should be closed. I'm pretty sure there wasn't any intention of allowing conforming implementations to define additional non-_ keywords. At least, that's my interpretation of the proposed standard..