-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix segfault when involing "lex" without specify the output "-o" and … #2
base: master
Are you sure you want to change the base?
Conversation
…make it work as specified in the "lex.1" man page
good job, let me know when you're done and this can be merged. |
… a variable that can be used uninitialized (detectd by valgrind)
In several interesting grammars they use The idea is to somehow compile kmyacc and lex to webassembly to do the heavy lifting and then run the resulting lex/parser directly through the browser. |
no, but feel free to add support for it. my personal plan with this project was to completely replace flex[0] in sabotage linux, but it turned out that too many packages use advanced flex features like reentrancy. [0]: flex is a giant unreadable hairball full of ifdefs and bugs and depends on GNU m4 and several external m4 files |
btw, when evaluating parser generators for own lagnuage projects the most interesting candidate i found was http://repo.hu/projects/byaccic/ |
I have some patched/extended parser generators here too https://github.com/mingodad/lalr-parser-test , I'm looking now on |
About reentrancy I already have a working reentrant scanner manually modified from the one generated by |
definitely interesting, i'd happily accept a PR |
Just don't specify an output filename and the code generator would try to write to |
so as i said above, |
It was segfaulting for me with one of several lex files I was testing, but right now I don't remember which one. |
…make it work as specified in the "lex.1" man page