I'm pretty sure that the reason is:

{
   # do loop stuff to be done at least once
   last if BREAK-CONDITION;
   # do middle loop stuff  <<< This part was left out
   redo;
}
[download]

which I'd still use while(1) for. Plus it allows you to do:

{
    # read next line
    last if NoMoreLines
    # extract item from line
    redo if NoItemInLine
    last if EndOfItemListFound
    # categorize item
    redo if WrongItemCategory
    # check for updates
    redo if NoUpdatesThisCategory;
    # check permissions
    last if NoUpdatesAllowed;
    redo if ThisUpdateNotAllowed;
    # do update
    redo if NotFatal;
    # handle fatal error
    # (note, no "redo" here so this part isn't really
    #  part of the "loop", just stuff to do once unless
    #  "last" gets triggered above.)
}
# done with items
[download]

where it is very easy to throw in a new check or new code in. But, as I said elsewhere, I find that power to be too easy to abuse. YMMV.

        - tye (but my friends call me "Tye")

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.