I was thinking more along the lines of copying the variables in the CFINCLUDE into the var scope, but I see that we'd need it bidirectional. Some manner of attribute (or maybe attribute*s*) could still handle the job though.
:) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Hastings Sent: Friday, May 07, 2004 3:11 PM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] CFINCLUDE forces var scope into arguments? > Maybe we could convince MM to add an attribute to CFINCLUDE like > "LOCALIZEVARIABLES={true,false}" to control this behavior. This has really good idea but lets call it something else. 'localize' means something else entirely. ---------------------------------------------------------- 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]
