I think that cfinclude is not cut + paste, and it IS the expected behavior that you cannot have CFC-specific tags within an included template. cfargument and cfreturn are integral parts of the cffunction tag, and it's obvious that they need to be present in order to create the appropriate method signatures. I have been using CF since pre 4.0, and I'm not suprised at all by this behavior, nor do I think it is anything close to a bug. CFML has expanded, and this is a growing pain. The fact that CFCs have a different extension should clue us in to the fact that they do not behave the same as a .cfm. I do agree that the docs are confusing, however... they should be annotated.
-dave ---------------------------------------------------------- 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]
