Re: Good practice or not to close the file before System.exit(1)?

From:

Lew <noone@lewscanon.com>

Newsgroups:

comp.lang.java.help

Date:

Fri, 22 Apr 2011 22:10:59 -0400

Message-ID:

<iotcfi$gno$1@news.albasani.net>

Patricia Shanahan wrote:

markspace wrote:

Patricia Shanahan wrote:

There is no problem using exceptions inside main, as long as you catch
them, so that they don't get thrown from main.

During development, throwing exceptions from main is fine because it
gives the developer the most about of useful information.

Yes, I was over-simplifying a bit.

I disagree. Throwing exceptions from main() provides no benefit that logging
doesn't provide better.

I'm using "main()" as a catch-all term for the top business layer of an
application, be it a Java application, applet, web app, service or whatever.
The observable behavior must conform to the problem domain being solved by the
application. Emitting implementation-level messages at the business-domain
level is inappropriate unless the business domain *is* the implementation.
Even there, there is a conceptual difference between the business domain and
the implementation domain.

Design your business logic to be business logic. DO NOT make the mistake of
"temporarily" inserting inappropriate code thinking, "We can pull this out
later for production." Later doesn't come around enough to count on that.

Design it right from day one and do not stray from being good.

--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg