In my opinion - a getter and setter is better for one main reason - even if you don't need to do anything special with the get or set, if you start off using them, you won't screw yourself later if you need them. In other words, build for the future.
======================================================================= Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc Email : [EMAIL PROTECTED] WWW : www.camdenfamily.com/morpheus Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Phillip Cave [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 30, 2003 9:08 AM > To: CF-Talk > Subject: CFCs - property access best practices > > > Hello everyone, > > I'm trying to get a feeling for what people are doing with > cfc's out there in the real world. Are people accessing > properties directly in their cfc's as in: > > someObject.firstName = "Phillip" > > <cfoutput> > #someObject.firstName# > </cfoutput> > > Or, are people actually taking the time to create "getters" > and "setters" > like: > > someObject.setFirstName = "Phillip" > > <cfoutput> > #someObject.getFirstName()# > </cfoutput> > > I want to go the route of "getters" and "setters", but I'm > really interested as to what is going on with real projects. > > Thanks, > > Phillip > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
