I do not really see anything bad with leaving off the arguments scope even though I never do it. What amazes me is when I see a UDF that references a variable within the variables scope of the page calling it. An example is this current app I have been brought in on recently. Within the applciation.cfm it has some UDFs and within one of those it has things like #someVar# well #someVar# is not an argument nor is it even a variable set within the page. What it is, is some variable set on some page within the application that later calls that UDF. Things like that are fun to go and debug, fun if you like headaches. Things like that are also why I tend to always put in a scope if one is available to put in.
On 5/21/07, Rebecca Younes <[EMAIL PROTECTED]> wrote: > > You should note that function arguments are automatically placed in the > local function scope, so there is nothing conceptually wrong with using the > unprefixed form in this case. Obviously, since it's the first scope checked, > there is no performance impact either. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278818 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
