I have written a parser or two. I have a few suggestions if you plan on writing your own parser.
- Prepare to devote the next few months if you plan to write a real, generalized, marginally useful parser. This is hard.
- Buy This book. Ingest all of it. Then, you are ready to write a useful parser.
Now, if you plan on writing a simple method to "parse files for your research", get our fellow monk davorg's book Data Munging with Perl. You won't really leave with the knowledge required to chose between LR and Recursive descent parsing depending on the Chomsky's hierarchy level of your grammar... but you will probably be able to do something quite useful. If you are planning on parsing, you shouldn't dismiss Parse::RecDescent so quickly as overkill, it's pretty sweet. And, with the advent of Perl 6, it will pretty much be "in core"...
-
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.
|
