single exit point : Java Glossary

single exit point
There is a school of thought that a method should have only one return statement. In general, this is a good idea. A return buried in a method disguises the program logic. However, some programmers sometimes take this notion to preposterous extremes. Some programmers will happily add 5 levels of nesting, and add a couple of booleans to avoid having a second return statement. I think a return or two at the very beginning of a method to handle the various empty cases is perfectly legit, and is not in the least confusing. If there are large numbers of returns, the logic is also clear. The danger is a sneaky return buried in the middle of the method.

CMP homejump to top You can get the freshest copy of this page from: or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror)
http://mindprod.com/jgloss/singleexit.html J:\mindprod\jgloss\singleexit.html
logofeedback Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : feedback email If you want your message kept confidential, not considered for posting, please explicitly specify that.
mindprod.com IP:[65.110.21.43]
view BlogYour face IP:[38.107.179.211]
You are visitor number 11.