You're putting the horse before the cart. Before you start worrying about the exact implementation, one needs to show the reason and purpose for the feature in the first place. You didn't provide any justification whatsoever for these changes, or mentioned any thoughts on the effects of the changes.
You even pretend that // doesn't exist. Don't you think people will have a problem with two names for the same operator? The word "teachability" has come up in discussions about new features. Having two operators with the same name would detract from teachability, for one.
The low-precedence version (to be named dor or err) was intentionally rejected (for reasons unknown to me). Do you have any new arguments that was presented then?
-
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.
|
