>>Sounds like a good reason to only have 1 RETURN, at the bottom
>>of the routine.
>
>I know, I know, top-down and all. But sometime sticking to this religiously can add a BUNCH of code to a routine.

Hiya Erik,

Well, yeah, but if the code is functionally cohesive, probably not. When a routine starts to get longer than I think it should be (20+ lines), that's a red flag to me that the routine isn't as cohesive as it should be. At that point I start re-examining the design of it. I get sloppy sometimes and it does happen more often than I'd like.

BTW, by the phrase "top-down" I assume that you're not referring to the top-down design methodology.

BTW2, nice pic. I didn't know who that person was when I first saw it.:-)

George

Ubi caritas et amor, deus ibi est