You are essentially building a compiler from 4D to perl. In addition to the modules mentioned above, it is also possible to build your own
top-down recursive descent parser. Each sub would represent a nonterminal and terminals generally correspond to regexes. Translation can either be done as you parse or by walking the parse tree afterwards.
I have hand-built parsers a number of times with good success. It allows one to really understand the nature of the language and customize as needed. Hand-built parsers can also be faster than P::RD, but this may not be a big consideration except in development of the compiler itself.
Whether you use the hand-built or module approach, I would recommend reading up on compilers to avoid pitfalls (such as ambiguous grammars) that would show up in either case. The best book I know of is "Compilers: Principles, Tools and Techniques' by Aho Sethi and Ullman.
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.