comment on

I look forward to your talk in Vienna.

I presume you are going to cover Damian's Parse::RecDescent - I would hope that you do so in some detail. Although it doesn't cover every situation, it is a tool that can enable parsing applications to be developed rapidly. When it comes to P::RD's autotrees, I wrote a module Parse::RecDescent::Topiary that assists in getting the trees in the shape you want them (properly constructed objects), rather than how Parse::RecDescent generates them.

It may be worth covering the history, and including YACC and LEX in the scope. Knowledge of bottom up parsers and how they differ from top down, is useful.

--
wetware hacker
(Qualified NLP Practitioner and Hypnotherapist)

In reply to Re: Writing Interpreters, Compilers and Translators in Perl by rinceWind
in thread Writing Interpreters, Compilers and Translators in Perl by Moron

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks