I used Parse::RecDescent in Data::HTMLDumper to give control over how the html tables actually look. I'm also using it on a new project which attempts to describe a web application in a single file, which I parse with Parse::RecDescent so various backend modules can generate things like controllers, Class::DBI subclasses, sql to build the database, etc.

Since I am self taught, I find the recursive descent style easier to understand, explain, and fix than the LALR style (with its shift/shift and shift/reduce conflicts). Using the trace option usually makes it easy to find where the parse went south.

I do notice the speed, but it is fast enough even for the moderately complex task of parsing my web app definition files (the current app has a 400 line definition). But this is a development tool. I can certainly wait 25-45 seconds for my the parser and backends to produce the basics of my whole app.

I'm also glad to see that grammars are coming to Perl 6. That may give a speed benefit, but it should also help vi with color highlighting.

Phil