29 Apr
2010
29 Apr
'10
3:44 p.m.
Hello!
That choice does exist yet unless you plan to do it?
The choice exists: either leave the current work-around, or change it to your work-around. Neither is a proper fix.
Right, neither is an ideal fix but at least mine is "correct" and doesn't cause REJECT to be defined inside flex, causing warnings. I don't understand your reasoning, you rather keep the buggy REJECT instead of renaming the bison token REJECT to Reject because it doesn't look as "pretty" anymore? Jocke