Re: Flex vs. POSIX 1003.2-1992 repeat operator {} precedence

[John W. Millaway]

I propose this solution:

We distribute with flex a version of lex that is posix-compliant. Building flex
on your system will also build 'lex'. If the user decides that posix compliance
is more important than performance, clarity,  and usability, then she should
invoke `flex -l`, in which case, flex passes the buck to 'lex'. No existing
flex scanners will break, the flex parser doesn't need to be hacked, and flex
is free to grow as a tool.


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/