Yeah, that's very much the crux of it. The reason, as you point out, is that someone decided that making get/set methods for instnace data was a good default thing to do. In general, you don't just start adding methods all over the place (too much work), except for the get/set methods in beans (because tools do it for you), so that's where the problem most often manifests itself.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Raymond Camden > Sent: Monday, September 15, 2003 10:49 AM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Getters and Setters WAS: DB and OO question > > > > > > Adding unnecessary set/get methods will likely encourage future > > developers to misuse your classes... > > Could one say that the this argument can be broken down to, do not use > unnecessary methods, which is something we should know anyway, but tend > to forget when it gets to methods that relate to object properties? > > -Ray > > > ---------------------------------------------------------- > 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] > ---------------------------------------------------------- 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]
