Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I think a methodical translation of the XML TR to a Perl 6 grammar would be a great asset to Perl 6 as a platform (user perspective) and would equally serve as a benchmark for the usefulness and performance of the grammar language (developer perspective).

    Further, once we have a realisation of the the original vision that the Perl 6 parser itself be a grammar overloadable by the program being under execution, this XML grammar could be used to implement something very much like Javascript’s E4X, without the need for any support within the Perl 6 specification itself (in contradistinction with the E4X being an explicit extension of the base Javascript language).

    And really, if done well (ie. using the specification as the guide in order to ensure completeness, comprehensiveness and compliance), an XML parser isn’t actually that scary a beast to write. And there’s an extensive pre-existing test suite, too.

    Now, this is a project in its own right, and thus I expect that even if you see my point and agree with it being worthwhile, I doubt you’ll be eager to have another hairy yak…

    But I wanted to argue that case.

    • Agree on all points, including the one about that being a separate project. I'm likely to do the bare minimum for Hitomi, and then we'll iteratively try to converge on something clean/fast/maintainable.

      I might mention that Karl Rune Nilsen (krunen++) started building an XML parser at the post-NPW hackathon. It's still in its early stages, but perhaps someone intent on writing the XML parser Aristotle envisions would still like to consult krunen for ideas. Synergy++.