My experience is that industry-standard formats aren't.
I mean, yes, they do exist, but more often than not,
they're a de facto standard because everybody in that
industry uses the same software for the same task.
Further, I find that Parse::RecDescent is more often useful
to parse either a) Extremely complex grammars like the
SQL example above, or b) Proprietary formats of things like
part numbers, internal file formats, etc.
If BAI::Format were truly useful, it would certainly be
much more useful to write it as a full-blown module (spit
out the code that Parse::RecDescent creates before eval'ing
as a starting point), than as a grammar file that needs to
be parsed before even starting to process the BAI file(s).
So, overall, while it'd be nice to have, say, SQL available
as a grammar, I don't think most people's Parse::RecDescent
creations would be either a) useful to anybody else, or
b) be able to be released to the public without having your
ass sued off.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
