Aye, I was thinking that if the "template" knew that there was a construct like "query:[ stuffstuffsstuff ]" that it could just absorb it and try to parse it separately in the perl block for that rule.

However, I'm concerned that "stuffstuffstuff" may need to deal with matching up square brackets and string literals that include brackets, to accurately find the end of the stuff and the close of the query.

It's much like the magic that Perl must use to identify the proper beginnings and endings of regular expressions in code, all while allowing weirdities like s###. (I hope my case ends up being simpler.)

--
[ e d @ h a l l e y . c c ]

In reply to Re^2: using two Parse::RecDescent parsers together by halley
in thread using two Parse::RecDescent parsers together by halley

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.