The single vs multiple point of exit argument has been going on for
years, made more intense by the arrival of the newer development theories.
Personally I can't decide. I think it foolish to not to exit at the top
of a procedure if some major item is missing (that business object you
need hasn't loaded) but I can see the benefit of single exist points for
the main code.
So overall I use single exit point in my main code but allow multiple
exit points in the set-up/checking code.
Erm, that would be 'multiple, single point returns'. I think I'll write
a book about about it... ;)
--
Michael Hawksworth
Visual Fox Solutions
[EMAIL PROTECTED]
www.foxpro.co.uk
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
