2024-02-27 01:23:33 <zelgomer    > yes, but lex and yacc are power tools that, when you use them, sparks and flames fly out and blemish the thing you're trying to craft
2024-02-27 01:24:04 <zelgomer    > they generate code that is so offensive i don't want to work around it
2024-02-27 01:42:33 <dsmith      > flex and bison are a little better.  But Parser Combinators seem to be all the rage these days.
2024-02-27 02:10:50 <Al2O3       > https://en.m.wikipedia.org/wiki/Parser_combinator   if you need to see something of this real, but with its own home-grown (maybe not now but in the old days it was) lex-like analyzer, look at SenseTalk, an X-Talk language.
2024-02-27 02:12:00 <Al2O3       > nearly 35 years ago, it was spun as a project in 89/90 to form the programming language that was the backbone of HyperSense, then Eggplant, and eventually part of a larger suite of products now doing AI-image based inferencing for automated testing.
2024-02-27 02:12:36 <Al2O3       > I do believe its the only surviving X-talk language in use at any level, for anything meaningful today.
2024-02-27 09:41:35 <veltas      > user51: The reason YACC looks forthish is probably because it's a DSL
2024-02-27 09:42:18 <veltas      > zelgomer: I'm firmly convinced the right way to write a parser is manual recursive descent, not using a generator
2024-02-27 10:14:21 <user51      > Obviously, a recursive-descent parser generator!  :P
2024-02-27 10:14:51 <GeDaMo      > That's essentially what parsing expression grammars are
2024-02-27 10:15:15 <user51      > Watch out, he's gonna link to that paper again! PART while you still can!  :P
2024-02-27 10:15:23 <GeDaMo      > :P
2024-02-27 10:15:45 <user51      > http://www.vpri.org/pdf/tr2010003_PEG.pdf