You could start off with all of them being private, then put the ones you want in the "this" scope to make them public (or put all ones not private in the this scope).
<cfset this.methodName = variables.methodName>
I've been experimenting with the opposite: beginning with some public and making them private. For example, the init() function is private, but once initialized by an external source it shouldn't be initialized again. But rather than deleting the init() function with StructDelete(this, "init") I transfer it to the private scope so if the object determines it should re-initialize itself (er, grammatically incorrect, but the action of resetting all of the values) then it can.
<cfscript>
Variables.init = This.init;
StructDelete(This, "init");
return This;
</cfscript>--
Ben Curtis
WebSciences International
http://www.websciences.org/
v: 310 478 6648
f: 310 235 2067----------------------------------------------------------
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]
