In a perfect world you would be right about @Deprecated - but I have
seen an example in the 1.6 SDK where a method has been @Deprecated
with the 1.6 release, along with some nice comments on how to do
things "the new way", only to find that in this case @Deprecated
actually means the method has been 'modified' so that it has
effectively become:
@Deprecated
public method()
{
return;
}
So, if you're unsure, or your "Compatibility" code which is still
using the older (now deprecated) methods/classes suddenly starts
misbehaving - download the Android source and go wabbit hunting!
Doug
On Oct 13, 8:14 pm, jotobjects <[email protected]> wrote:
> Deprecated classes and methods still work but they are a notification
> to developers that they will be dropped eventually so new code should
> not use them and updates should stop using them. There should be a
> compiler warning if you use an @Deprecated method and it should show
> as deprecated in the API documentation. From what I have seen that
> last part does NOT happen in 1.6 - you have to look at the source code
> to find out what is deprecated or pay close attention to compiler
> warnings.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
