The real question is why you'd ever use CFINCLUDE inside a CFC. I've though about going that route, but the only reason is to get around the shortcomings of the tools available. If you need to reuse a block of code inside a CFC, use a function, don't use an include. Problem solved.
Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Roland Collins > Sent: Friday, May 07, 2004 2:05 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] CFINCLUDE forces var scope into arguments? > > I agree that you need to do _something_ to make the variables > accessible, I > just don't think copying them to the variables scope was the > right decision. > It defeats the purpose of even bothering with "var" in a > function that uses > an include, to say nothing of the havoc that threading can wreak on > unsuspecting components using this methodology. > > Roland ---------------------------------------------------------- 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]
