I just did a bit of digging with getPageContext() and it looks like CF
creates a copy of the arguments scope in the local unnamed scope rather than
the other way around.
Ah, I should have read the whole thread before responding to Barney! Yes, you are correct.
Why they need to put a copy of the arguments scope in the function local
scope is open to conjecture, but I wouldn't be surprised if it was so that
backward compatibility wouldn't be broken when people upgraded from 6.0 to
6.1.
Also correct.
This is kinda weird, but also kinda interesting because it means you can
change the value of an argument to a function if required by manipulating
the function local scope value, but you can still find out what the initial
value was by accessing it as arguments.x. That may not be a common thing to
do, but it's useful to know you can.
...and I wouldn't advise writing code that relied on that! :)
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]
