That is because you come from a compiler world. Pure runtime languages don't have these issues including CFML until recently.
Cut'n'paste behavior for includes occurs only in languages that process the include prior to semantic analysis, e.g., C's preprocessor. Which "pure runtime language" are you referring to that has includes that behave just like cut'n'paste?
It is certainly syntactically valid; it just requires that the function's meta data isn't known until runtime.
It is not syntactically valid:
Context validation error for tag cfargument. The tag must be nested inside a CFFUNCTION tag. The error occurred in /home/tomcat/webapps/cf61/null/naked.cfm: line 1 1 : <cfargument name="foo">
Besides the fact that you can't open and close tags in different files, cfincludes really do act like cut'n'paste. For example, try including a binary file.
Please give a concrete example - I'm not sure how including a binary shows cut'n'paste behavior and I'd really like to understand your argument.
Regards, Sean
----------------------------------------------------------
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]
