avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: Re-precating (?) classes (was: RE: What is a Parser?)
Date Sat, 01 Feb 2003 22:31:41 GMT

Noel J. Bergman wrote:
> Nicola,
> Why do you deprecate something?  

When we recommend that something is not used anymore, as is the case 
with Java API deprecation. It also means that we won't support it in the 

> Do you deprecate something because there is
> a better way, or because there are good reasons not to use something?


> Why *deprecate* Component and related items?  Is there a reason not to use
> Component, or is it just better to be able to use an Object that is not a
> Component?

In the Java API methods are deprecated even only when there is a name 
chenge (ie the addition of a set* to names).
The fact that it is better to be able to use an object directly is a 
sufficient reason for deprecation.

Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

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

View raw message