Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!umd5!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: <7388@brl-smoke.ARPA>
Date: 1 Mar 88 21:25:10 GMT
References: <8016@elsie.UUCP> <8020@elsie.UUCP> <7352@brl-smoke.ARPA> <8022@elsie.UUCP> <7365@brl-smoke.ARPA> <2801@haddock.ISC.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8

In article <2801@haddock.ISC.COM> karl@haddock.ima.isc.com (Karl Heuer) writes:
>I believe that to avoid colliding with the user's local variables, keywords
>(like machine-specific #defines) must begin with a double underscore or an
>underscore followed by an uppercase letter.  I thought one of the more recent
>Drafts covered this issue.

ADO and I don't seem to be able to find the part of the draft that so constrains
keywords (as opposed to macro names and external identifiers).  I'd appreciate
a reference to the proper section number, or something.