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"...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.