+1 to Peter Bell's reply. I'm quite happy to have one of these deity objects (usually a server- or application-scoped singleton referred to as a "kernel") but it usually works out better for it to manage a whole pantheon of lesser demi-gods who are then designed to do perform their role well (hail Bacchus! More wine and cheese!)
On Tue, Jun 9, 2009 at 4:21 AM, Peter Bell <[email protected]> wrote: > > Delegate some of the objects responsibilities to a composed object or > (if it fits better), split the object into multiple interacting > objects with different responsibilities. Try to think about the Single > Responsibility Principle and looking for highly cohesive, lightly > coupled objects. > > > > On Jun 8, 2009, at 2:13 PM, Henry wrote: > >> >> What techniques can one use when one found the # of methods in an >> object is too high? >> >> Actually, when is it 'too high'? >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
