Two or more versions of our shop are running on the same machine. One shop is running with a older version of the CFC framework - maybe a customer is updating the old shop. The newer version would use the old CFCs.
I assume you're talking about a shared host environment? If so, that sure has an interesting set of problems to address...
I see - it would be great if <cfargument type> could also take an expression. This would solve all our problems.
<cfargument name="foo" type="any">
<cfif isObject(arguments.foo) and getMetadata(arguments.foo).name is myFooType>
... body of function ...
<cfelse>
<cfthrow message="FOO passed to FUNC is not of type #myFooType#">
</cfif>
(I don't recommend doing this but it would provide the variable type checking you seem to want...)
I am not sure about <cfcomponent throws an extends> - I think they are also not accepting expressions.
Correct. "extends" is a compile-time attribute - it can't be a variable.
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]
