If you can't just print out the entire line as toolic suggested, then you will need to break up that monster regex.

Regex's are an all or none thing. It isn't that the variables are going out of scope. They either all get set if there is a match or none do. Since the match fails, none of the variables $1,$2, etc are set and you get those lovely undefs even for fields you know have matched one of the captures in the regex.

Instead, you will need to split the line into fields and check for valid data in each field one by one. If each field passes your validation test, pretty format the lines and print that line to the "good lines" file. If not, print the fields of interest to the "bad lines" file.

In reply to Re: Capturing parentheses out of scope by ELISHEVA
in thread Capturing parentheses out of scope by iangibson

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.