On Sun, 14 Nov 2004 17:28:07 +0100, Magnus Wege <[EMAIL PROTECTED]> wrote:
> In the overview it is mentioned that you shouldn't use the variables scope
> ("avoid using").That's very out-of-date as it refers to bugs in CFMX 6.0 that have been fixed for two years (with CFMX 6.1). > Though Nando is right that the "this" scope is available to > the caller which breaks the encapsulation paradigm. "this" scope is the equivalent to "public" data members - and all the literature out there will tell you not to use public data members. "variables" scope is the equivalent of "protected" data members. If your object needs state information, it will use "variables" scope. "variables" scope exists for the lifetime of the CFC instance (which depends on the scope in which the CFC instance itself is stored). "var" - not exactly a scope, but you should use it to declare any and all variables that should be local to a specific function call. Such variables are created fresh for each function call and exist only inside that function. > -----Urspr�ngliche Nachricht----- And you really need to trim your posts... [many hundreds of lines deleted] -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Breeze Me! -- http://www.corfield.org/breezeme Got Gmail? -- I have 1 invite "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- 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 [EMAIL PROTECTED]
