tag:blogger.com,1999:blog-7278144.post7114521943791593308..comments2023-09-16T17:37:07.333+02:00Comments on Francisoud's Blog: Why the @Deprecated annotation sucksBenjamin Francisoudhttp://www.blogger.com/profile/14823114858391962141noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7278144.post-66334402240733039432013-09-26T11:16:48.840+02:002013-09-26T11:16:48.840+02:00@Deprecatd helps compiler to generate warning mess...@Deprecatd helps compiler to generate warning message irrespective of JVM vendors period. There is no other benefit. SUN/ORACLE should put some more thoughts on method usability before lending it to user. Completely agree with you, it should have a String parameter at minimum.Vivjhahttps://www.blogger.com/profile/13221728866907516759noreply@blogger.comtag:blogger.com,1999:blog-7278144.post-18374451837502015392008-05-16T17:23:00.000+02:002008-05-16T17:23:00.000+02:00Drop a bug on Sun. No @Deprecated sucks. There w...Drop a bug on Sun. No @Deprecated sucks. There was no thought put into it by the Sun engineers and it should have a parameter to specify a message to what you should use in it's place. maybe even the ability to provide a class and method you should look to. That would allow tools like javadoc to use the annotation.<BR/><BR/>This is just another example of Sun engineers coming up with a good idea, but poor execution and application of the technology. It's all over the place with Sun created java APIs. Note to Sun: It's not just enough to have a cool architecture. You have to DO SOMETHING WITH IT WITH IT THAT'S MEANINGFULchubbsondubshttps://www.blogger.com/profile/06708078598697844829noreply@blogger.comtag:blogger.com,1999:blog-7278144.post-74508888871244592322007-05-25T10:04:00.000+02:002007-05-25T10:04:00.000+02:00A leap backward ? You already explained what is th...A leap backward ? You already explained what is the technical difference between the two tags : "@Depreacted annotation will be pick up by any compiler".<BR/><BR/>And about the use, effectively it seems redundant. But don't forget that one is about programming/algorithm/API specification, and the other is about the documentation. What would you think about the redundancy of the parameters ? The names of the parameters are used twice. And in fact one defines the parameter, and the second refers the first one to defines its documentation. We can view the "deprecated" tags the same way. One defines that the function is deprecated, the other documents it.<BR/><BR/>So there is some redundancy (due to the referencing), but no "sucks" for me.Anonymousnoreply@blogger.com