Having my in the same context as a trailing if is usually bad form. As far as I can tell, the variables are declared regardless of the outcome of the if and are scoped to the block.

In plain english, this means that the split is not occuring, but the variables are there, and you are still printing because there is no conditional on the print.

That's why I suggested using a next call to skip to the next line. If it is a comment, there's no point in calling either split or print, is there?

Update:
For additional clarity, here's an example of what's happening: 
while (<INFILE>)
{
     my ($infile, $dir, $type);

     if (!/^#/)
     {
          ($infile, $dir, $type) = split;
     }
     print "$infile $dir $type\n";
}

[download]

In reply to Re^3: Context of "if" statements? by tadman
in thread Context of "if" statements? by ibanix

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.