Hi Robert, I think there are pros and cons for using that approach:
Pros - smaller components - less code to maintain - more flexible Cons - too ambiguous (you don't know what the component holds just by looking at it) - increased coupling between objects (calling objects must know the names of internal data structures) - forces order of calling the setter before getter (when requested arrays are not previously defined. will throw an exception rather than something expected like an empty array) Justin "The sender believes that this E-mail and any attachments were free of any harmful and malicious code or defects when sent. The sender is not liable for any loss or damage arising in any way from this message or its attachments. Confidentiality Note: This e-mail is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, is prohibited. If you have received this e-mail in error, please inform the sender, and destroy the original message and all copies." You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
