Re: Exception Misconceptions
On Dec 20, 3:39 pm, ta...@mongo.net (tanix) wrote:
In article
<35f3b2ed-8303-4249-8b12-3f85b4907...@s31g2000yqs.googlegroups.com>,
James Kanze <james.ka...@gmail.com> wrote:
[...]
Java's portability is
limited to machines which have a good JVM.
Correct.
Which isn't many.
Well, about 90% of total market from what I know.
Our markets may not be the same, or perhaps we have different
definitions of a "good JVM". And Sun has, I believe, made
considerable progress. But when I was working in Java, about
the only implementation I'd have considered passably good was
the one for Windows; the others (including the one for Solaris)
were really very basic interpreters, with really excessive
runtime overhead. And in the markets I've worked in in the
past, Windows is a non-runner.
5) Robustness.
And THAT is where these nasty exceptions come in handy.
You'll never be able to write a stable code, and I mean
TRULY stable, if you do not use exceptions.
Explain how applications have been running for years, without
interruption, and without using exceptions.
Well, THEORETICALLY, it can happen even without using
exceptions. In reality, it is just a joke.
It's no joke. It's an everyday reality. Most of the phone
switches and transmission systems go back to a time before
exceptions, and they work. Year in, year out, without
interruption.
For one thing, without exceptions your code becomes a huge
pile of spegetti code and I know what I am talking about.
Apparently not, because I've worked on very large code bases,
without exceptions, and without any spaghetti. Exceptions do
make certain things easier, but you can live without them.
(The application in question was written before C++ supported
exceptions.) Exceptions are a useful tool, for certain
things, but like all tools, you can do without (at some
development cost) if you have to.
Sorry. I can not agree with you on this one.
I think you are somehow predisposed AGAINST exceptions.
Not at all. But I was programming long before they were
generally available, and we still managed to write robust and
maintainable applications.
--
James Kanze