On Thu, Apr 30, 2009 at 10:50 AM, Tom Gibara <[email protected]> wrote:
> That's only a cosmetic change though. Instead of calling, say, prepare() >> and it throwing an exception, you now have it return some token that tells >> you whether or not it succeeded. >> > > That's only a cosmetic change if you think that throwing an exception is a > first-class way of returning state; not to mention the performance > implications. > > It doesn't really give you any extra functionality or information. >> > > What it gives you is a meaningful way of managing the knowable state of the > media player within client code. > Define 'meaningful'. Those states that are knowable, you can already know about with the current API. Those states that the MediaPlayer might transition to on its own, the API you suggested isn't going to help with either. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
