Or store your CFCs in a shared scope, and have same-named *local* variables within functions :-(
Adam Cameron Senior Application Developer Straker Interactive E: [EMAIL PROTECTED] T: +64 9 3095252 F: +64 9 3092797 W: www.straker.co.nz -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kenney Sent: Tuesday, 6 July 2004 4:12 p.m. To: [EMAIL PROTECTED] Subject: Re: [CFCDev] Serialization of CFCs And hopefully you don't have "var" scoped variables that have the same name as "variables" scoped one. If you do, "Oops!". On Tue, 6 Jul 2004 15:31:07 +1200, Adam Cameron <[EMAIL PROTECTED]> wrote: > If you have this sort of thing in your function: > > <cffunction> > <cfset var something=something> > <cfinclude> > </cffunction> > > Then something like this takes place, behind the scenes: > > <cfset structAppend(variables, [unnamedFunctionLocalScope])> > > So you'll end up with a variables.something variable, lurking around > in the CFC-wide variables scope. > > Adam Cameron > Senior Application Developer > Straker Interactive > > E: [EMAIL PROTECTED] > T: +64 9 3095252 > F: +64 9 3092797 > W: www.straker.co.nz > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Postmaster > Sent: Tuesday, 6 July 2004 3:21 p.m. > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] Serialization of CFCs > > So... are you saying "un-named" varaibles in the function?... or are > you saying var.myVariable? Could you be just slightly more detailed... > (pardon the begging... heh) so the rest of us will benefit by your > research. > > John > > ----- Original Message ----- > From: "Paul Kenney" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, July 05, 2004 6:54 PM > Subject: Re: [CFCDev] Serialization of CFCs > > > If you use <cfinclude> inside a <cffunction> tag in a component, all > > of the function scoped variables are moved to the "variables" scope > > for that component. Its a nasty little bug that utterly lays waste > > to > > > thread safety when using cfinclude in a method call... but I say, > > just > > > don't do that! > > ---------------------------------------------------------- > 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] > ---------------------------------------------------------- > 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] > -- Paul Kenney [EMAIL PROTECTED] ---------------------------------------------------------- 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] ---------------------------------------------------------- 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]
