This is interesting because these UDFs still respect the notions of
PUBLIC and PRIVATE, kind of like they *were* almost methods, but... not.
The <cffunction> tag always allows you to specify the access= attribute, regardless of whether it is inside <cfcomponent> or not.
It actually sounds to me as if it's exactly what I identified it to be, to be honest... Another bug with CFCs and <cfinclude>.
Nope. It's designed that way. And it makes perfect sense when you understand the model behind the language.
- without polluting the methods in your CFC.Not quite sure what you mean there. You mean in the meta information? The component browser?
Correct. They don't show up as methods in the metadata (even if you put access="public" on them - because of course that is irrelevant in a standalone UDF).
I just tested this and indeed it's the case. That's quite useful to know (and always good to learn the good with the bad!).
Glad you at least like that part of the equation...
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]
