Hi Thomas, On Thu, Jul 10, 2008 at 10:17 AM, Thomas N. <[EMAIL PROTECTED]> wrote: > 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.
Does "Open Declaration" (F3) help? I've seen that eclipse doesn't show the deprecation comments in the popup, but they are there. > 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?) If you talk about us adding hints, I think that they are there, but Eclipse doesn't show them. If you've found any concrete place where it lacks the comment, give a pointer and anyone familiarized with the code can add it. If you talk about Eclipse giving the hints in the deprecated comment, I'm looking yet for it too. > 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. ;-) This is a good practice that we should do always, it doesn't matter how much 'obvious' it could seem. -- Cheers, Christian López Espínola <penyaskito>
