Wow, what amazing discovery, somebody should perlbug this in a hurry

The bug is that it breaks $1 and m//atching operator, and it doesn't warn... 

$ perl -wle " $_ = 333; for $1 ( 666 ){  print $1 if /(...)/;  }"
666

$ perl -wle " $_ = 333; for $1 ( 666 ){  local our $1; print $1 if /(.
+..)/;  }"
Use of uninitialized value $1 in print at -e line 1.

[download]

No warnings are issued, matching is broken in a different scope, its a bug ... kind of amazing people don't trip on it every day

Kinda related
Lexical $_ in given/when vs. BLOCK arguments
 Bug #115834 for perl5: Successfull match $_[0] =~ /foo(.+)/ overrides $_[0] if function called as foo($1)

In reply to Re^7: Getting an unknown error (foreach $1 breaks m//atch) by Anonymous Monk
in thread Getting an unknown error by andybshaker

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.