Hi Dov and all,
On Mon, Aug 28, 2017 at 3:12 PM, Dov Grobgeld
wrote:
> Another issue is that if you today need to write a parser in lex/yacc,
> then you probably made a bad decision along the way. There are today lots
> of well supported meta formats with excellent and well tested parsers, e.g.
The concepts remained the same (see the Dragon book of Aho&Ullman; a great
book, BTW).
As long as the new libraries and parsers implement the same algorithms,
everything is OK.
>From what I see, the only fundamental thing that changed since those
ancient days, is the higher need to support streamin
Another issue is that if you today need to write a parser in lex/yacc, then
you probably made a bad decision along the way. There are today lots of
well supported meta formats with excellent and well tested parsers, e.g.
json, xml, yaml, config/ini, and your ROI is better spent integrating one
of t
I see that the thread is still alive, so just wanted to say that it's a
de-ja-vu for me.
I've used to be a LEX/YACC master somewhere in the previous century (i.e.
the previous millennium...).
I not only used it for writing compilers, interpreters and parsers, but
also built a cool library based on
