And I've encountered some features, described in camel book(s), which just don't work in some (or most, or modern ) versions of perl, for example:
001 while ($sth=~/sth(sth)/g)
002 {}
shortcut. This used to work in 5.000, stopped working in 5.6 because of broken
optimisation. I reported the bug, but apparently this was considered a buglet, and left as is.
This forced me, (and for example Apache::ASP project) to instead use unefficient replacement:
001 $mycopyofstring=$sth;
002 while ($mycopyofstring=~s/sth(sth)/) {
003 }
I don't know what you're trying to show here, but the second example is a syntaxt error (Substitution replacement not terminated).
The point here, is that important features of language appear and disappear at will, thus you've got to stay in-loop all the time, keeping and eye on changes, hoping that what you've learned won't be thrown out of the window next sumer.
Important features? I think you mean experimental features.
MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | ** The third rule of perl club is a statement of fact: pod is sexy. |
-
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.
|