Re: [codec] DecoderException superclass [WAS: StatefulDecoders]

[Tim O'Brien]

I think the introduction of EncoderException and DecoderException in and 
of itself was a mistake in the first place.  Creating hierarchies of 
exception just for the hell of it isn't a hobby I can maintain.

IMO, Encoder and Decoder are similar to Reader and Writer which both 
throw IOException.

Tim

Gary Gregory wrote:
It also makes me wonder why De/EncoderException do not subclass a
"CoderException", CodecException? Just thinking aloud...
gg


-----Original Message-----
From: Tim O'Brien [mailto:[EMAIL PROTECTED]
Sent: Monday, February 23, 2004 18:00
To: Jakarta Commons Developers List
Subject: Re: [codec] DecoderException superclass [WAS: StatefulDecoders]
Gary Gregory wrote:

Alex suggests below that IOException would also make sense.

Opinions?
I'm don't have strong feelings either way.  If EncoderException were to
extend IOException, or if Encoders threw IOExceptions instead of
EncoderException.  Encoder and Decoder were experiments, most people who
use Codec instantiate an object like Base64 or Soundex directly.  If
these interfaces and exceptions need to evolve, let's do it.
Tim

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]