To me, this is the sort of problem that should be described in terms of a grammar, and then handled using Parse::RecDescent. (I have used that module quite extensively and it works very well.)
Let me give you one small tip if you go that way... Part of your code will consist of the grammar and Perl code that will be compiled on-the-fly into it. This is a great place to put a use statement(s) that will link to any subroutines that you find that you need to make use of in the grammar code.
Anyway, the advantage of this approach is that you describe the structure of the language being processed and let the parser do the magic. It takes a bit of practice to get the grammar right, heh, but the parser can handle the mechanics of regex’ing and backtracking so that your code doesn’t have to. You can extend it to do more things without getting buried.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||