That depends on your definition of "as expected"... ;) I would *expect* cfinclude in CFCs to work the way it does in CFMX6.1 - a cfinclude'd file is a separately compiled entity so it clearly should not behave like cut'n'paste...Clearly you are in the minority in terms of expectations in this thread, but I am curious. Do you think it is expected that cfinclude shouldn't be allowed to include the entire function body e.g. the following.
<cffunction name="foo">
<cfinclude template="foo.cfm">
</cffunction>Not matter what your position on including UDFs, I believe that the above is perfectly valid, but in many cases isn't supported by CFMX in CFCs. It is supported by BD, so again there is an issue for us to be aware of. Further, the fact that in CFMX a cfincluded file is a separately compiled entity is an implementation detail that shouldn't affect CFML developers. CFML developers never needed to understand implementation details before and they shouldn't now. Further, such a description doesn't begin to explain why the behavior of cfinclud differs depending on the context in which it is used.
-Matt
----------------------------------------------------------
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]
