On Mon, Sep 27, 2010 at 12:59 AM, SpaceJack <[email protected]> wrote:
> BTW why it's terrible? :) Altering a base class's properties or behavior based on some flag that's expected to be set by the derived class(es) just seems like a bad design. The base class should be doing whatever it is that is that makes sense at that inheritance level - it should not have any knowledge or responsibility for changing what it does based on what's happening "up the chain". For example, what happens when you add a new derived class down the line? You would have to update the meaning of your "what" member and update the base class to handle this case as well. Doesn't sound pleasant. Hope that makes sense. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
