Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site caip.RUTGERS.EDU
Path: utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!caip!NEVILLE%umass-cs.csnet
From: NEVILLE%umass-cs.csnet@CSNET-RELAY.ARPA
Newsgroups: net.micro.amiga
Subject: keywords - read the manual!
Message-ID: <656@caip.RUTGERS.EDU>
Date: Mon, 9-Dec-85 06:59:24 EST
Article-I.D.: caip.656
Posted: Mon Dec  9 06:59:24 1985
Date-Received: Wed, 11-Dec-85 03:50:30 EST
Sender: daemon@caip.RUTGERS.EDU
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 24

From: "Neville D. Newman" <NEVILLE%umass-cs.csnet@CSNET-RELAY.ARPA>


Perry Kivolowitz  pointed out that the Lattice C compiler would choke
on code such as

zero_out(entry)
int  *entry; {

    < ... >
}

because the identifier  "entry"  was reserved as a keyword.  The fact that
that this code would compile on version 6 and 7 Unix systems, and possibly
others, does NOT mean that Lattice adds anything to the language definition.
On the contrary,  K & R  [Appendix A, sec 2.3, "Keywords"] point out that
"entry" is reserved for future use as a keyword.  VAX-11C [section 2.1.6 of
the v1.0 paperback] also points this out.  Note that some implementations
go further and reserve "void", "fortran", "asm", etc.  Since K&R is usually
recognized as the standard (in the absence of ANSI) it is valid to flame
about "asm" being a keyword, but definitely not "entry".

						-neville
					    neville.UMass@CSnet-relay (ARPA)