>Bruce,
>
>I really think the design criteria for not using constructs like EXIT and LOOP are "behind the times" at this point. How many loops have you written lately that are more that a dozen lines of code recently? I'll bet in general your loops are a lot shorter in lines of code than they used to be. I know mine are.
>
>I've worked on systems before where a loop spanned several pages of code, and there yes exits from inside were a big annoyance. Heck let's start a campaign to add a computed GOTO to FoxPro then we can really start reeking some havoc. *s*

Heck, you can even simulate spaghetti right now with GO top, GO bottom, SEEK(something), SKIP -1, etc., placed all over within a large loop :)

>
>With a loop that is 15-20 lines of code, fits within your code edit window, I don't have any problem putting an early exit condition to save a more complex code structure just to avoid using LOOP/EXIT because they are considered bad programming style.

Dave, it's nice to find someone that shares my attitude, you're quite right, the days of monolithic program code with huge loops are past now...