Hi, I sometimes stumble over calls to deprecated code when working on other things, and then in eclipse I hover over the striked through code to see the Javadoc. Then, when I find just the deprecation tag and no hint what to use instead, I leave it because of time constraints or lack of knowledge, which makes me feel a little guilty.
Is there a way to add hints about the nondeprecated alternative, so that usage of deprecated code can easily be changed by any developer? (Maybe at least from now on, when adding a deprecation annotation?) I hope this is not a too big request. Even a hint that states "an alternative is not obvious" would be helpful, because then I would feel less guilty when I leave it as it is. ;-) (Or am I supposed to investigate and "de-deprecate" the calling code anyway?) Regards, Thomas -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
