News for hackers. Stuff that matters.
Re:Why not to use (f)lex, yacc or bison by pansa2 on Thursday March 05, 2020 @03:46AM (#22491972)
For general-purpose languages, yes, but there are some exceptions. Ruby uses yacc, and Python uses a custom LL(1)-ish parser generator, which is in the process of being replaced by a custom PEG parser generator [0].

[0] https://github.com/gvanrossum/pegen

Re:Why not to use (f)lex, yacc or bison by regularfry on Thursday March 05, 2020 @04:21AM (#22492128)
Ruby's yacc parser is my usual go-to for telling people how not to do it. That thing's terrifying.
Re:Why not to use (f)lex, yacc or bison by jknoepfler on Thursday March 05, 2020 @09:41AM (#22493849)
To be fair, ruby is not a fun language to machine-parse.
Re:Why not to use (f)lex, yacc or bison by regularfry on Thursday March 05, 2020 @11:27AM (#22494980)
Oh absolutely. As a user, I love the ruby syntax. As a potential contributor to the codebase? NOPENOPENOPE.
Re:Why not to use (f)lex, yacc or bison by chrisseaton on Thursday March 05, 2020 @04:32AM (#22492176)
Ruby doesn’t use yacc as intended though - it’s definitely not a good advert for yacc.