Re: Exception Names

From:

Tom Anderson <twic@urchin.earth.li>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 28 Mar 2009 13:59:24 +0000

Message-ID:

<alpine.DEB.1.10.0903281358040.19324@urchin.earth.li>

On Fri, 27 Mar 2009, Lew wrote:

rossum wrote:

On Fri, 27 Mar 2009 11:58:20 +0000, Tom Anderson
<twic@urchin.earth.li> wrote:

InputStream.read should throw an EOFException instead of returning -1 at
the end of a stream. Checking return values for special values is goofy C
bullshit that we shouldn't be doing in the 21st century.

It may bee goofy but it is very likely to be a whole lot faster.
Throwing and catching an exception is probably going to be a lot
slower than checking the return value.

Besides, there's nothing exceptional about reaching the end of a stream.
One would venture to say that one nearly always reaches the end of a
stream, *unless* something exceptional happens.

There's something entirely exceptional about asking an object for
something (a next byte) that it can't give you. If a method can't do what
you've asked it to do, it should throw an exception.

tom

--
Hesgadin. It was in two parts - both of them silent. I remember this map
came with a letter accusing me of stealing eggs. I had never understood
the relationship of the map to the accusation. I still don't, but I'm
grateful for the map.