Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix-wizards Subject: Re: Is this correct action for the c compiler/preprocessor ?? Message-ID: <2076@umcp-cs.UUCP> Date: Sat, 2-Nov-85 19:40:48 EST Article-I.D.: umcp-cs.2076 Posted: Sat Nov 2 19:40:48 1985 Date-Received: Mon, 4-Nov-85 01:48:07 EST References: <8510301207.AA27158@ucbvax.berkeley.edu> <270@cornell.UUCP> <473@basser.oz> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 24 In article <473@basser.oz> john@basser.oz (John Mackin) writes: >In article <270@cornell.UUCP> jqj@cornell.UUCP (J Q Johnson) writes: >> Most versions of pcc ignore stringness (``"'') when looking for tokens >> for macro replacement. ... K&R are silent on the lexical issues >> involved, so this cannot be considered incorrect. >I couldn't let such a glaring misstatement pass. Page 207, sec. 12.1: > ``Text inside a string or a character constant is not > subject to replacement.'' Surprise, surprise, this is actually ambiguous. When I first read this I assumed it meant `text inside a string or character constant anywhere'. It really means `text inside a string or character constant (except in the replacement portion of a macro)'. Unfortunately the former is the more reasonable interpretation (naturally---it is mine :-) ), so the ANSI standard has settled on that, and introduces some new `experimental' `stringizing' macro expansion features. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@mimsy.umd.edu