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.
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.