Article View: comp.std.c
Article #5309Re: preprocessing: character- or token-based?
From: Henry Spencer
Date: Tue, 23 Aug 1988 17:39
Date: Tue, 23 Aug 1988 17:39
16 lines
1088 bytes
1088 bytes
In article <812@polari.UUCP> rlb@polari.UUCP (rlb) writes: >#define aplus +a > +aplus; /* one operator, or two? */ > >ambiguous in meaning. Can anyone point me (quoting exact passages :-) >to a place in the Standard which precisely defines what happens in this >case? It seems to me that the problem is that the Standard nowhere defines >the meaning of the part of translation phase 7 called "Preprocessing >tokens are converted into tokens." I think you've hit a genuine ambiguity here. It should probably say "Each preprocessing token is converted into a token.", which would eliminate the ambiguity. -- Intel CPUs are not defective, | Henry Spencer at U of Toronto Zoology they just act that way. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu
Technical Details
Message-ID:
<1988Aug23.173922.28086@utzoo.uucp>Path:
arc1-ca.pugleaf.net!utzoo!henryReferences:
<812@polari.UUCP>Show Full Headers
Complete Article Headers
Newsgroups: comp.std.c Path: arc1-ca.pugleaf.net!utzoo!henry From: henry@utzoo.uucp (Henry Spencer) Subject: Re: preprocessing: character- or token-based? Message-ID: <1988Aug23.173922.28086@utzoo.uucp> Organization: U of Toronto Zoology References: <812@polari.UUCP> Date: Tue, 23 Aug 88 17:39:22 GMT