I have mixed feelings.
In reading the RFC, there were a few examples I liked alot, like:
# Some become easier and more consistent...
($str = $_) =~ s/\d+/&func/ge; $str = subst /\d+/&func/ge;
($new = $old) =~ tr/a/z/; $new = trade /a/z/, $old;
# And these are pretty cool...
foreach (@old) { @new = subst /hello/X/gi, @old;
s/hello/X/gi;
push @new, $_;
}
foreach (@str) { @new = trade /a-z/A-Z/, @str;
tr/a-z/A-Z/;
push @new, $_;
}
$gotit = 1; print "Got it" if match /\w+/, @st
+r;
foreach (@str) {
undef $gotis unless /\w+/;
}
print "Got it" if $gotit;
So there are some advantages to be gained here. Problem is, if people mix standards in their code (ie using m/// when it makes things short and easy, but using match() when that makes things easy) is that going to make it harder to read code over time? (I guess that might always be a problem with backwards compatibility...)
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.