One rumored "fix" would be to add an attribute to CFIMPORT to instruct it to
wait until run-time to determine the path. This would (if true) just really
kill performance for those templates that used it (since I assume they would
probably be compiled on demand every time), but it would allow this kind of
thing without breaking backward compatibility.
Yes, it would certainly kill performance - as would allowing extends= to be a runtime attribute. So I very much doubt such a 'fix' is even being considered...
Sean A Corfield -- http://www.corfield.org/blog/
"There are no solutions, only trade-offs." -- Thomas Sowell
----------------------------------------------------------
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]
