As an aside, it can be useful to rig-up a “data walker” object that will iterate through a data-structure ... search http://search.cpan.org for “walker” ... and then perhaps maintain a push-down stack of such objects. Once, I solved a similar problem by devising a walker that would call a specified sub (coderef ...) when it found a matching node. Each subroutine in turn made the decisions that needed to be made at that level, and spawned another walker-instance to proceed further. Thus, the walkers handled the task of navigation while the subroutines made the case-specific decisions. (It was a lot easier to do than to describe.) I did it this way because, while I could not predict what the shape and depth of the structure would be, I could describe the logic as a small number of reusable, node-specific cases.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||