Producing a Go parser from the language specification mechanically, mostly (modern-c.blogspot.com) 3 points by 0xjnml 3y ago ↗ HN
[–] bediger4000 3y ago ↗ Good article. This little line interests me:> For the last part a PEG, actually in this case an EBNF interpreter is needed.Not sure how I should parse this. Should I read it as:For the last part, a PEG interpreter is needed. Actually an EBNF interpreter is needed.Because a PEG is just a spec, you can't substitute an interpreter for it [–] 0xjnml 3y ago ↗ Thanks for the feedback, I tried to add a paragraph explaining it a bit more.Please let me know if it did not help, thanks.
[–] 0xjnml 3y ago ↗ Thanks for the feedback, I tried to add a paragraph explaining it a bit more.Please let me know if it did not help, thanks.
2 comments
[ 10.2 ms ] story [ 202 ms ] thread> For the last part a PEG, actually in this case an EBNF interpreter is needed.
Not sure how I should parse this. Should I read it as:
For the last part, a PEG interpreter is needed. Actually an EBNF interpreter is needed.
Because a PEG is just a spec, you can't substitute an interpreter for it
Please let me know if it did not help, thanks.