No, I don't think the OP wants that, and I don't think any other person rooting for certification of Perl wants that.
What they want is have a specification which says that "EXPR if CONDITION" is 1) legal, and 2) states what it means. There are benefits to having a specification constructed by a specifications body. The benefits gets bigger if there are more players. Perl, being a relative small language, with just one vendor (that is, just one entity that produces Perl) the benefits are smaller than for instance C, with millions of coders, and dozens of compilers.
I don't know whether Perl would benefit from getting a standard. It depends on what your goals are, I suspect. If you want to get more people to program Perl, and have it being used in more companies, you want specification more than if you want to give more flexibility to the implementors.
-
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.
|
