To be able to safely use this.varName in a read-only manner. Set-able from internal, but only readable from external. "Write once, read many."
If that is not possible, then I would like VB-similar setters and getters where you call: <cfset obj.varName = "mike"> Where CF "knows" that I just called the "setVarName" method in "obj". M!ke -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Merrill Sent: Wednesday, May 11, 2005 4:08 PM To: [email protected] Subject: RE: [CFCDev] LTOs What do you need that the variables scope inside a cfc doesn't give you? Dave Merrill > After some discussion with people, I've been thinking about the use of > the "this" scope in the LTO and whether it's appropriate. You can > easily change the values in the LTO because of its' use. > > Won't it be so much nicer when Adobe adds Protected or Static > variables to CFCs? > > M!ke ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
