Nowhere was any mention made about leaving the methods exactly as generated. Say I need custom getters for 50% of fields, but I want to use getters for everything, just to be consistent, and to isolate the object from future implementation changes. Chances are remarkably good that that the generated function will remain almost entirely unchanged; just the CFRETURN tag will need modification.
I agree that mindless get/set methods are bad, particularly when they are autogenerated, but that doesn't mean that I can't use autogeneration to get 95% of the way to what I need. Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Matt Liotta > Sent: Wednesday, July 14, 2004 12:00 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Beans: Explicit vs Implicit arguments? > > If the getters and setters are so easy to script up then they > shouldn't be > there in the first place. Using getters and setters is a > debatable practice > to being with, but when you throw code generation into the > mix the practice > is surely bad; some would even say the practice is evil. > > -Matt ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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]
