evelopers List" <[EMAIL PROTECTED]>
> Subject: RE: [codec] DecoderException superclass [WAS: StatefulDecoders]
>
> > > I think the introduction of EncoderException and DecoderException
> > > in and of itself was a mistake in the first place.
> > > Encoder an
> > I think the introduction of EncoderException and DecoderException
> > in and of itself was a mistake in the first place.
> > Encoder and Decoder are similar to Reader and Writer which both
> > throw IOException.
> I agree fully.
I disagree fully, as I will explain.
> Decode and encode operat
Hi,
Let's take the simplest topic first which is the Exception issue.
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
>
> 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
>>> Encoder and Decoder are similar to Reader and Writer
>>> which both throw IOException.
>> Note that this would no longer hold true in a push model codec library,
>> since it would not actually perform I/O.
> True, having StatefulDecoder.getDecoded() throw an IOException seems
> fishy.
Agreed.
Noel J. Bergman wrote:
Encoder and Decoder are similar to Reader and Writer
which both throw IOException.
Note that this would no longer hold true in a push model codec library,
since it would not actually perform I/O.
True, having StatefulDecoder.getDecoded() throw an IOException seems
fishy.
breakage acceptable?
Gary
> -Original Message-
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 23, 2004 19:31
> To: Jakarta Commons Developers List
> Subject: Re: [codec] DecoderException superclass [WAS: StatefulDecoders]
>
> I
> Encoder and Decoder are similar to Reader and Writer
> which both throw IOException.
Note that this would no longer hold true in a push model codec library,
since it would not actually perform I/O.
--- Noel
-
To unsub
mons 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
velopers 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 EncoderExc
