Hmm, you do make some good points and I appreciate it. However, I don't know that I'd want to pull the plan out of the grammar as one could use that to easily write some code to parse a bunch of regular TAP strings to validate their TAP producer. At that point, the only required semantic check would be to ensure that test numbers correspond to the correct test line. That would make semantic analysis much simpler since the grammar, as a declarative tool, is more likely to be correct.

I like the rest of what you've done, though. Still, maybe I'm just smoking crack :)

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^2: Revised TAP Grammar by Ovid
in thread Revised TAP Grammar by Ovid

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.