Keep in mind that the external template is compiled and executed separately from the actual function. It's not a textual include of the file content before compilation or execution, it's a totally separate object being called that is outside the function object that actually knows about it's local variables. In other words, whether the scope is named or not, you still have to copy the values to the variables scope for the external template to access them.
Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jim Davis > Sent: Friday, May 07, 2004 1:47 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] CFINCLUDE forces var scope into arguments? > > Well... I think the simple solution would have been to create > a local NAMED > scope instead of local unnamed scope. > > Then the CFINCLUDE could be given access that the named > entity just as it's > given access to the named variables scope. > > Jim Davis ---------------------------------------------------------- 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]
