Sean:
Given your access to the CF developers, perhaps you could check rather
than just "suspect"? ;)
I guess it's not in the docs (at least I could not find it), but it's
been a "known" way to instantiate components since 6.0. And, since it
works, it's clear a relative path is not inherently unacceptable.
Sean Corfield wrote:
On 6/8/05, Nathan Dintenfass <[EMAIL PROTECTED]> wrote:
I know there are Macromedians on this list -- any of you care to give us
some insight here? Is it really something like Mark opines -- a random
implementation decision, or are there solid reasons for the choice?
I suspect the behavior is a random side-effect of the implementation
because the docs state that extends takes the "name of parent
component" and everything refers to component names not paths. I think
the fact that on Windows a component name with \ instead of . works as
a relative path and on Unix a component name with / instead of . works
is "by accident".
Am I missing something in the docs? Can anyone point me at anything in
the docs that indicates the component name can be a path name?
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
