> You're also falling into the getX()/setX() trap that I recently > blogged... If you have a 1:1 relationship between your data > members and > your public getX()/setX() methods then you are not encapsulating > anything. >
Are you saying that if you don't do anything special with your get/set than it's not worth the time? What about setting up getX/setX in case you _eventually_ have special conditions for setting data members? In other words, planning for the future where getX may need to do a security check or somesuch. ======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
