Re:PEG.js - parser generator for JavaScript
by barrkel on Wednesday March 17, 2010 @01:37PM
(#1199135)
I know all of that. My point is that the if/else problem really is an ambiguity (i.e. it is a language bug, not just a problem you have to get around in parsing), and problems similar to it crop up when your tool doesn't alert you to first/follow conflicts, in LL(1) parlance. That PEGs encode the implementation strategy inside the declarative grammar is a flaw, in my opinion, not a benefit.
[ Parent
| on HN ]
Re:PEG.js - parser generator for JavaScript
by cynicalkane on Wednesday March 17, 2010 @01:47PM
(#1199165)
In programming, ambiguity is bad! Explicitly encoding disambiguation rules in the grammar is a good thing, just like it's a good thing in functional pattern matching, in Prolog... I'd be interested to hear any reason why you would want to not disambiguate a grammar in any language designed to be computer-recognizable.
Re:PEG.js - parser generator for JavaScript
by barrkel on Wednesday March 17, 2010 @02:27PM
(#1199271)
Here, read this:
http://compilers.iecc.com/comparch/article/05-09-114
In particular:
"Yes, this is "the" problem with PEG's. / implies ordering of the search (parsing) space. You need to order your / operators so that special cases (e.g. longer matches), so that they appear first. Unfortunately, if you don't do this, nothing will tell you you have a problem with your grammar, it will simply not parse some inputs. To me this implies that if one wants to use a PEG to parse some input, then one must exhaustively test the parser."
Hopefully the thread therein will describe my issue better than I have thus far.