avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject RE: Removing dep on CascadingException in collections
Date Sat, 30 Mar 2002 18:37:48 GMT
> -----Original Message-----
> From: Jeff Turner [mailto:jeff@socialchange.net.au] 
> 
> On Fri, Mar 29, 2002 at 08:54:00AM -0500, Berin Loritsch wrote:
> > > -----Original Message-----
> > > From: Jeff Turner [mailto:jeff@socialchange.net.au]
> ...
> > > I would like to make Derived no longer extend Base, but
> > > otherwise maintain API compatibility by reimplementing Base's 
> > > public methods. Any code that typecasts Derived to Base will 
> > > break. I'm wondering, do we (or should we) guarantee this 
> > > sort of compatibility?
> > > 
> > > In my case, I have:
> > > 
> > > public class CascadingRuntimeException    // in framework
> > > 
> > > public class BufferOverflowException 
> > >     extends CascadingRuntimeException // in Excalibur's
> > > collections package
> > 
> > We can probably do it in this case.  If people cast the 
> Exception to 
> > anything, it was RuntimeException or BuferOverflowException.
> 
> Good. Btw, I see the same situation in the Event code.. :)

The Event code is still scratchpad--even though I want to
finalize it soon.  We can fix it.



--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message