I tried it after working with m/\G/gc regex first. I was
surprised how easy it was converting my regex to a
Parse::RecDescent grammar.
I have begun to see where the talk in perl6 about rules
rather than regex is coming from.
I like the feeling in perl of being able to pull yourself
up by your bootstraps, learning as you go. At the same
time, I wonder why whatever I read in the perl5 stuff never
tried to lead me across the bridge from regex.
Now I'm reading Dick Grune's online book about parsing.
I've only written one simple grammar. The feeling of
mastery however is motivating. I think I will be on the
lookout for ways to parse more things from now on.
All this was generated by my first simple parsing need,
however, of course.
-
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.
|
