> I can verify it. In fact, I am very disappointed that this > is the way MACR > chose to implement this.
They didn't really have a choice. The template that you CFINCLUDE is an independent block of CFML, it has no knowledge of anything function related. In other words, it has to function the same way whether it's in a function or not. On the surface level you can do that, but you forget that the CFML compiler is doing a lot of work dereferencing variables and such. The scope search, for example, is dependant on context. In a function, you use local variables first, but in a template, you don't even have access to that scope. Once we finally get a decent IDE for CFML (or even a really pathetic IDE), it won't be a big deal to have HUGE CFCs, and consequently includes won't need to be used for keeping them more managable. Unfortunately, right now all we've got is text editors, but such is life. Cheers, barneyb ---------------------------------------------------------- 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]
