Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Gathering experiences with Parse::RecDescent

by Corion (Patriarch)
on Oct 20, 2005 at 06:48 UTC ( [id://501550]=note: print w/replies, xml ) Need Help??


in reply to Gathering experiences with Parse::RecDescent

I found Parse::RecDescent nice, as I am fond of recursive descent parsers - the top-down approach of parsing seems elegant to me and it can produce nice, sensible error messages. The surrounding utility functions to automatically generate ASTs etc. are also nice.

That said, I found two showstopping drawbacks to Parse::RecDescent. First of all, it's horribly slow for moderately complex grammars (Javascript in my case). Second, if you have a syntax error in your grammar, the error messages range from obscure to opaque, and you can't go and fix the parser itself, because Parse::RecDescent is written in itself and the distribution (at least at the time when I used it) didn't include the source grammar but only the generated result. From time to time, it wouldn't raise an error at all, or raise an error in the wrong place.

Personally, I recommend Parse::YAPP nowadays for any serious parsing (if it has to be done in Perl). The drawback of Parse::YAPP is that it needs a left-recursive grammar where Parse::RecDescent wants a right-recursive grammar (or vice versa), but the resulting code is nice, the driver for the parser is simple and could be written in XS to get a moderate speed gain.

  • Comment on Re: Gathering experiences with Parse::RecDescent

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://501550]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (4)
As of 2024-04-19 04:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found