Re: RFC: enum instead of #define for tokens

[John W. Millaway]

> If Flex adapts the same mangling scheme, then `...' within actions should
> be mangled into C/C++ labels. Thus,
>   "!=" { return `!=' }
> might be legal. Or one may even has that as default.

I doubt it will ever fly. What about '\012', which is legal C, but should not
be "mangled"? One thing about flex, it doesn't mess with your C code, and
that's probably a good thing to preserve.


> But
>   . { return yytext[0]; }
> would not work. It is still possible to reserve this character range, so
> that Bison can issue the proper error message.

But remember we're looking ahead to unicode.


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/