It might be useful to apply “state machine” logic here. Or even to approach the parsing task using a tool such as Parse::RecDescent (which has become a very well-known tool to me as of late...).
Basically, it seems that the best way to describe this problem is that “the proper interpretation of what is in front of me now, depends upon what surrounds it; on what has come before.” That contextual knowledge can be represented in a “state.” And, the greater task might well be expressable using a grammar, hence my suggestion of a true parser.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||