>Hi George,
>
>>Walter,
>
>>I'm not putting up a argument one way or the other here.
>
>>When processing speed is paramount, then you program in that direction. When it isn't, you program for maintainability.
>
>Absolutely. However in this thread there was an argument for speed, whether or not to use the evils. I got carried away in finding the most optimal solution to the problem.
>
>>I've always thought that there's performance and the perception of performance. A user isn't going to notice when something is 1/10th of a second faster. A user will notice when a minor modification can't be implemented quickly and easily.
>
>Absolutely. Therefor I expressed (as you did) in this thread that the difference between a FOR ... EXIT ... ENDFOR and a DO WHILE solution is neglible.
>
>And in this light we agree that maintainability is far more important than a minor performance difference.
>
Walter,

Won't argue for a jiffy (1 / 60th of a second). While the argument can be advanced that we should all code for optimal speed, I don't buy it.

If, from the outset, an application needs to perform at the utmost speed possible, then you design for that. Otherwise, you design to maintain, and if performance then becomes a consideration, do what's necessary to achieve it.