Thanks for the good advice. m!ke ________________________________
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Kotek Sent: Friday, May 09, 2008 8:56 AM To: [email protected] Subject: [CFCDEV] Re: Appropriate Use of Parent Object In general, yes, that is part of the point of a superclass: to avoid duplication in the child classes for common behavior. (The real purpose of superclasses is polymorphism but that is another topic). In theory one should only put behavior in the superclass if it is shared by *all* of the subclasses. If some subset of the subclasses has duplicate behavior, then another layer of inheritance may be necessary to stick to this rule. In practice (and especially in CF where long inheritance hierarchies get expensive) the answer is less clear. I would say that, pragmatically, you could just go ahead and do it, and refactor later if there any issues arise. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
