In general, "Favor composition over inheritance". http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Professional/dp/0201633612
On Mon, Mar 10, 2008 at 9:36 AM, boyracerr <[EMAIL PROTECTED]> wrote: > > Hello to all, > > I'm very interested in the Cake 1.2 concept of behaviors. However, > since there isn't much discussion around about them yet, I'm keen to > here how people are using them in practice. > > What is the line between deciding that particular functionality should > be implemented as a behavior and putting it in a superclass? > > In many cases it is obvious, for example with the Tree or > SoftDeletable behaviors. Clearly, objects of many very different types > will find these useful and they should be behaviors. > > Take though for example objects of type Bus, Truck, Car. These are all > Vehicles; logically and traditionally this would be an abstract parent > class. You could also make it a behavior though: what makes you decide > which is which? Any advantage with using Behaviors versus > SuperClasses, other than that you can have many behaviors but only one > parent? > > Thanks, > Ben > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
