As always, it's a trade-off. In this case, if the advantage of having email wrapped up into its own class is very high (perhaps the behavior of email is expected to change often, or needs to be reused in many other classes), then that advantage is worth the performance cost of creating it for the objects that need it. However, I wouldn't just go do this with all properties of all objects. It has to be done for a valid reason, with an understanding of the pros and cons.
In general, small classes ARE preferred. Smaller objects are much more likely to be cohesive. The larger an object gets, the more likely it is that is might be doing too much and the more likely that future changes will be more difficult to make. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
