New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flex v 2.6.4: comment in VParseLex.l is causing my flex to barf... #1252
Comments
Original Redmine Comment Wow, good job debugging that. I'm wondering if the below patch also works for you? That is use C style comments. My worry is at some point there might be another ' added by mistake and perhaps C style is better supported?
|
Original Redmine Comment Looks like a C style comment does fix this issue.
|
Original Redmine Comment Fixed in git towards 3.448. |
Original Redmine Comment In 3.448. |
Author Name: Rob Stoddard
Original Redmine Issue: 1252 from https://www.veripool.org
Original Assignee: Rob Stoddard
The comment on line 591:
is causing my lexer to throw chunks. I have no idea why, it looks like a perfectly valid comment. It's the apostrophe (single quote) that is causing my lexer to give me the following error:
which itself is amazingly misleading and annoying. I had to find the issue by cutting out chunks of the lexer and running it until the issue went away.
The text was updated successfully, but these errors were encountered: