I think a repository of RecDescent grammars is an excellent
idea. I don't think they should be included in the module distribution itself for fear of excessive bloat.
A couple of alternatives:
-
Someone could volunteer to maintain a Parse::RecDescent::Grammar pseudo-module, that aggregates
all the contributed grammars. There could even be a front-end analogous to Regexp::Common.
-
We could just use Regexp::Common directly, by providing a
top-level $RE{grammar} namespace.
-
We could ask for a RECDESCENT (pseudo)ID on CPAN and use
that directory to house RecDescent grammars.
-
Someone could set up a web-site that allowed people to submit and then update their grammars
I would support any of these approaches, though, unfortunately, I don't have the spare capacity to implement any of them myself. Personally, I favour the P::RD::G approach, since it puts the grammars on the CPAN, in the correct namespace, where search.cpan.org is likely to draw them to the attention of potential beneficiaries.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.