News for hackers. Stuff that matters.
Re:Writing An Interpreter In Go (2016) by tom_mellior on Monday November 25, 2019 @10:41AM (#21629044)
I think "you plug a grammar into a generator, and you get back a function that maps character sequences to a syntax tree" can be enough understanding for a lot of use cases. Maybe you're more interested in any of the many other aspects that go into designing and implementing an interpreted language -- type checking, garbage collection, an efficient bytecode format and interpreter for example. But maybe you aren't, in which case I agree that case a hand-written parser might be right up your alley! There's no one size fits all.
Re:Writing An Interpreter In Go (2016) by greenshackle2 on Monday November 25, 2019 @11:24AM (#21629646)
You need a little bit more than that, cause if that is the limit of your understanding, you will have a bad time when the generator spits back an error message about reduce/reduce conflicts or whatever instead of a function.