I had always thought (as others comment) that $1 and friends weren't reliable after a failed match, but I
note that the following was added to perlre beginning
with 5.8.1:
NOTE: failed matches in Perl do not reset the match variables,
which makes easier to write code that tests for a series of more
specific cases and remembers the best match.
But perlre also says:
The numbered match variables ($1, $2, $3, etc.) and the related punctuation
set ($+, $&, $`, $', and $^N) are all dynamically scoped
until the end of the enclosing block or until the next successful
match, whichever comes first. (See perlsyn/"Compound Statements".)
and in your case you are actually leaving and reentering the enclosing block, which seems to make a difference:
$ perl -we'$_="FOO"; /^([A-Z]+)$/, print $1; $_="Foo"; /^([A-Z]+)$/; p
+rint $1'
FOOFOO
$ perl -we'for ("FOO","Foo") {/^([A-Z]+)$/; print $1 }'
FOOF
though it would be nice if it failed consistenly rather than
sometimes working and other times not.
-
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.
|