The VARIABLES scope inside a CFC is a bit more confusing. For implementation reasons I do not fully understand, the developers of CF decided that the VARIABLES scope should contain all methods of the CFC regardless of access type.
That's so unqualified calls to methods still work:
foo()
is equivalent to:
variables.foo()
regardless of access.
If you dump the VARIABLES scope you will also see that it contains "THIS".
Again, variables.this is really what you're accessing but we wouldn't want to encourage that!
I would consider both of those facts to be implementation details that you should ignore.
Agreed.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word '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]
