Aye, Mark... that's fairly rudimentary CFC stuff. The question was more along the lines of whether or not I can use "path.to.classes.foo" as the returntype in one CFC's init method and "foo" as the type of an argument to receive an instance of foo in  a method of another CFC. AFAIK, if you use "path.to.classes.foo" as a CFC type and "foo" as an argument type, it would error.

What confused me in Ray's original message was the reference to "just the last part making a difference." I know that you can use "foo" or "path.to.classes.foo" as the returntype for a CFC's init method... but whichever way you do it, that type must match the type argument for any method accepting an instance of foo as an argument. AFAIK, the whole type has to match, whether it's a path or just the CFC's name... hence my question regarding the "just the last part" comment.

As far as using slashes in your types, last time I read anything on the subject it's OS-dependent and unsupported... which makes it a highly risky thing to use in a production application.

Laterz,
J

On 4/28/05, Mark Mandel <[EMAIL PROTECTED]> wrote:
Jared -

Type has never had to be be the whole path -

  1. You can simply use the name of the CFC if they are in the same directory
  2. If you have a mapping, you can use the mapping as the root and work from there
  3. You can use a / or \ sytle sytax to do relative typing down a tree structure (but not up)
All of these options work for CFMX >= 6.1

Of course... this would all be better if CFMX had some decent namespace management...

Mark



--
---------------
-------------------------------------
Buy SQLSurveyor!
http://www.web-relevant.com/sqlsurveyor
Never make your developers open Enterprise Manager again. ----------------------------------------------------------
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).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]

Reply via email to