Hi Russell,

Yes, a near-religious subject, this coding 'standards' stuff.
I think you've got it about right, as long as the 'anal' part doesn't kick in.
It's really that bit that makes me suggest that it not be a "rule".
I too would guess that 90% of my code has one exit only.

cheers


>Wow, you really started a heck of a thread. I think one exit point generally makes for better code and it should be a "standard", keeping in mind that there are always situations that might arise to cause you to break the "rule". You say 90% of your code is single exit. I'd say that's somewhere around my percentage, though I really don't track it. If people ever say "you should NEVER have anything other than a single exit point", I'd say they're being a bit anal. Avoid it whenever possible, but don't sweat the times you break the rule.
>
>
>>Continuing PeterDeV's quest towards a set of 'excellent coding standards'...
>>
>>What is the value/purpose of "one exit point per code unit?"
>>
>>Isn't it time that this old chestnut was retired?
>>
>>I don't see an iota of **real** value to the practise, but I do see problems.
>>
>>Why do you follow the practise?... if you don't, why don't you and what static have you heard from others about it?
>>
>>Anticipating interesting replies,
>>JimN