Noel J. Bergman wrote:
Nicola,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 future.
Why do you deprecate something?
Do you deprecate something because there is a better way, or because there are good reasons not to use something?
http://java.sun.com/j2se/1.4.1/docs/guide/misc/deprecation/deprecation.html
In the Java API methods are deprecated even only when there is a name chenge (ie the addition of a set* to names).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?
The fact that it is better to be able to use an object directly is a sufficient reason for deprecation.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]