Oooh. I flagged this kind of stuff as "scary code" already before in the Monastery, I think.

The rule is "NEVER look at $1 unless it's conditionally based upon a successful match".

For your code, you might accidentally push the same value two or more times, since your push doesn't depend on the success of the match, so you'll end up grabbing the $1 of the prior match.

You probably intended something like this:

my @numbers; while (<FILE>) { push @numbers, $1 if /(\d+)$/; }

Another way to write that without using a push might be:

my @numbers = map /(\d+)$/, <FILE>;
which works because if the match fails on a line, you get an empty list (not a prior $1).

-- Randal L. Schwartz, Perl hacker


In reply to RE: RE: RE: Re: Why regular expression so hard?! by merlyn
in thread Why regular expression so hard?! by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.