Those "many cases for this there is no particularly good reason one was picked over the other" are most likely, I hope, the cases where I gave up on trying to figure out why the Android team chose to make the one 'abstract class' and the other 'public interface';)
On Jul 21, 10:28 pm, Dianne Hackborn <[email protected]> wrote: > On Thu, Jul 21, 2011 at 8:16 PM, Indicator Veritatis <[email protected]>wrote: > > > They do not pause to explain, for example ... why some classes are defined > > a public abstract classes, while very similar other classes are > > defined as interfaces. > > Well hopefully you generally don't care. And to be honest, in many cases > for this there is no particularly good reason one was picked over the other. > ;) > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
