The input string will be small; should I walk the string or walk the match object? As an exercise, treating the problem like a larger language appeals?
The idiomatic approach is not to iterate at all, but to define an action class with methods that generate the desired datastructures, and storing them in the ast attribute of the current match object.
The grammar chapter of our work-in-progress-book talks about this technique a bit
(it's also slightly outdated, and I plan to update it within the next few days). (Update: I've updated it both to match the current spec, and to work with current Rakudo. You can find the examples in the simplified_parsing branch on github.)
$match is supposed to work just like $/, yes?
Yes. And recent development versions of Rakudo also set $/ in Grammar.parse.
Since a few days Rakudo also supports the $/.perl method (Perl 6's built-in version of Data::Dumper), which shows you the structure of the match object.
- links to (nearly) everything that is Perl 6.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||