Well, the discussion has morphed into a debate as to whether always using arguments (as you propose) or never using arguments (my preference) is better. There's good sides to using it (consistency in that everything is scoped), and bad sides (I outlined several previously).
I should also mention that I don't want to completely eliminate the arguments scope from the language. It is absolutely required since we don't currently have method overloading. I need to append my zealous position and say that I have no problem at all using the arguments scope like an array, when the indexes are greater then the number of named parameters for the function. In other words, using 'arguments' like an array is perfectly acceptable for unnamed parameters. That's the only way to access them anyway, because they aren't moved to the local scope. Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Nolan Erck > Sent: Friday, March 19, 2004 11:54 AM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Unscoped references in CFSET within CFFUNCTION > > Am I the only one who sees this thread/problem as a non-issue > if you just always always always scope your variables (which > is recommended practice by Macromedia anyway)? > > I mean, yes it's interesting and good to know of the > underlying behaviors of CF, how things are copied to the > local scope, etc. But if you're concerned about "foo" being > "arguments.foo" or not, just put "arguments." in front and be > done with it. > > Right? > > ---------------------------------------------------------- > 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] > ---------------------------------------------------------- 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]
