I'd avoid statement labels ('LINE' in your sample) unless they are required. Especially in a small scope the target of loop commands is clear in any case and adding statement labels makes it look like more is going on than is actually the case.

Here's Essential Practice number 4 of Damian Conway's Ten Essential Coding Practices:

4. Label every loop that is exited explicitly, and every next, last, or redo.

I adhere to this best practice except in the most trivial circumstances. Whenever there's a natural, logical label to use (e.g., LINE, RECORD, ROW, FROG), I use it. It makes my intentions explicit and clear.

(See Perl Best Practices.)

In reply to Re^2: Another reason for perl beginners to read perldocs by Jim
in thread Another reason for perl beginners to read perldocs by Don Coyote

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.