Because these APIs are *not* considered public. They are very likely to change/disappear in the future and this will break the binary and source compatibility if you use these APIs. Consider these APIs private.
On Tue, Oct 21, 2008 at 12:48 PM, Shane Isbell <[EMAIL PROTECTED]> wrote: > If these non-public APIs are open, I don't see any reason why we can't use > them, as long as we peg our version of the application to the current G1 > distribution. That's how we have to do it in the Java ME space and I guess > that's what Google is doing too. > > Shane > > On Tue, Oct 21, 2008 at 12:27 PM, Shane Isbell <[EMAIL PROTECTED]> > wrote: >> >> >> On Tue, Oct 21, 2008 at 10:27 AM, hackbod <[EMAIL PROTECTED]> wrote: >>> >>> And further than that, people writing third party applications MUST >>> develop them against the SDK, not against the open source release. >>> Otherwise you can easily use non-public APIs, and thus break in a >>> future release. >> >> Of course, now that it's open-source, MUST is more of a suggestion, as >> there will be multiple distributions of Android deployed on devices. >> >> Shane > > > > > -- Romain Guy www.curious-creature.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
