You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2021. It is now read-only.
Of course pp and Hoa\Compiler ease the job, but a dev / debug mode allowing the developer to understand the grammar in some special cases, and giving verbose traces would be a real plus.
Resurecting an issue :-P
I have very important performance issue during parsing, and I would like to know what the parser has done to be so long. So, a list of rules it passed or not for each node could be interesting to improve anything...
A while ago I implemented a POC debug parser working with the dbg protocol.
It allows to put breakpoints in PP grammars and see which rule the compiler uses. If anyone is interested in using it/contributing/testing/whatever, I can try to make it work again and push it somewhere.
This seems very interesting ! I've made a tracer that plays every rules the parser passed through and am working on a viewer (like a video player, with rule breadcrumb and parsing progression (backtrack) ). Your work seems very good as well :-)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
writing grammar can be a tricky work.
Of course
pp
andHoa\Compiler
ease the job, but a dev / debug mode allowing the developer to understand the grammar in some special cases, and giving verbose traces would be a real plus.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: