cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: Re-precating (?) classes (was: RE: What is a Parser?)
Date Mon, 03 Feb 2003 14:04:19 GMT
Vadim Gritsenko wrote:

 > Berin Loritsch wrote:
 >
 >> #3 We can safely remove the Component interface (the source for most
 >>    deprecation warnings).
 >
 >
 >
 >
 > I'm trying to be cautious about removing it from public well-known 
interfaces. Users are writing code with assumption that they won't 
change, but once you remove Component interface from, say, Generator, it 
means user's code won't compile anymore without change.


What do you mean it won't compile anymore without change?

Of course it will.  You can remove interfaces at will.  If the class
still implements all the methods that are part of that interface, the
class will still compile.

The Component class is *still part* of the Framework JAR.  It isn't
going away until the Avalon 5.0 release which won't be here for quite
a while.

Do a little experiment.  Have an interface that implements Serializable,
which is also a marker interface.  Now have a class that implements the
new interface.  Next remove the Serializable interface from the new
interface.  Recompile.  Hmmm.  The class still compiles.

The only time you are going to have a compile time problem is when
the original interface is removed completely from the classpath.
That is not happening.


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message