I use it a fair amount, mostly for your last example type situation, when the 'C' code is more complex than a single line. I find it easier to read to keep the 'loop maintenance' and 'loop actions' code separate.
My most common example is probably a user-input loop: 'B' is while I can read from the input, and 'C' is the prompt/menu. (This assumes an interactive-only program, of course.) 'D' is the actual code to handle the different choices.
Yes, that could be put in the loop in most/all cases, but I like knowing where to look for each type of code, and that they won't interfere with each other.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.