This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Objective C lexer - small cleanup
- To: Stan Shebs <shebs at apple dot com>
- Subject: Re: Objective C lexer - small cleanup
- From: "Zack Weinberg" <zackw at Stanford dot EDU>
- Date: Thu, 28 Jun 2001 18:32:14 -0700
- Cc: gcc-patches at gcc dot gnu dot org
On Thu, Jun 28, 2001 at 06:13:09PM -0700, Stan Shebs wrote:
>
> Looks like a good change! I even rolled across the hall and tried
> it out on the original author (Steve Naroff)... he had a question,
> and I couldn't be sure from inspection - is '@ objckeyword' or
> '@ /* cmt */ objckeyword' now valid? It looks like it is, and
> in fact it looks like "#define FOO interface" "@ FOO class ..." will
> work also. Since this would be a compatible extension of the
> existing language, it's not really a problem, just sort of a weird
> consequence as far as I can tell.
Yes, that is now accepted. I think it has been acceptable since the
introduction of the integrated preprocessor: the leading @ and the
keyword have been separate tokens since then.
That *could* be changed: cpplib could consider @ an acceptable
character to start an identifier with, in objc mode. In fact, that
would simplify the c-parse.in logic quite a bit more. I'll leave that
decision to you and the other people defining what the language is.
zw