Interestingly, that does work if you take out the "variables." and just use the name of the method (which, I must admit, I prefer for method calling to using "variables.method"). I wonder if that's related to why we can't use name/value arguments with super methods.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Stephen Milligan > Sent: Friday, March 19, 2004 4:55 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Unscoped references in CFSET within CFFUNCTION > > > [snip] > > That brings up another interesting thing that I only noticed the other > day... > > If you are calling a private method in a CFC from a public method > you can't > pass the arguments as name=value pairs: > > eg. > > test.cfc > <cfcomponent> > > <cffunction name="publicone" access="public"> > <cfargument name="arg1"> > > <cfreturn variables.privateOne(arg2=arguments.arg1)> > </cffunction> > > <cffunction name="privateone" access="private"> > <cfargument name="arg2"> > > <cfreturn "It works"> > </cffunction> > > </cfcomponent> > > > test.cfm > <cfset test = createObject('component','test')> > <cfset test.publicOne(arg1="test")> > > > Not sure if that is known behaviour, but it surprised me. ---------------------------------------------------------- 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]
