Re: Multiple returns vs. Single exit

 Way back in the old days coding standards pretty much existed to
overcome problems with the language.  One standard in FORTRAN was to
define all variables, which tried to overcome the fact that you could
use a variable without defining it, which means you can misspell a
variable name and get a spuriously generated variable whose contents
were unknown.

So, many companies had separate bureaucrats in charge of such things.
Java came along with much, much lower need for such stuff since there
are much fewer language deficiencies to overcome, but the bureaucrats
are still here and need to justify their jobs.  Tell them that
technology in the form of compiler detection of issues and using IDE
capabilities eliminates the need for standards, and that means they have
to find something useful to do.  They resist that heavily.



-----Original Message-----
From: Discussion of advanced Java topics.
[mailto:[email protected]] On Behalf Of Peter Booth
Sent: Sunday, December 30, 2007 10:45 PM
To: [email protected]
Subject: Re: [ADVANCED-JAVA] Multiple returns vs. Single exit

Almost always coding standards seem to waste much more time than they
save. The most effective "standard" I have seen wasn't a standard.  
Instead of a tedious dry document that describes "this is what we expect
our coders to do" we simply named a single (large) component as our
"Gold Standard that illustrates how we do stuff around here"

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com