I tend to agree with the suggestions of others that the second regex in the chomped <STDIN> section of the OPed code is simply failing to match, and the previous value of  $1 is persisting.

Try inserting the statement
    print qq{\$1 reset: '$1'} if 'foo' =~ /(foo)/;
between the first and second regex in that section and seeing what happens. If the second  'ZZZ' becomes  'foo' you will know what is happening (although not why the second regex fails to match, which I cannot understand myself).

In reply to Re: perl pattern match for end of string using STDIN and chomp by AnomalousMonk
in thread perl pattern match for end of string using STDIN and chomp by cbolcato

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.