> I have a CF5 compatible user-defined function like this:
>
> function jsqfCommit(formname) {
> arguments[1] = request.tapi.js.qf(formname) & ".commit";
> return request.tapi.call("request.tapi.js.call",arguments);
> }
>
> This works beatifully in CF5 (don't get me started on the
> functions that
> used arraydelete() on the arguments array), but in CF MX when
> the arguments
> array is passed to request.tapi.call, it contains the
> original value of
> formname, not modified value provided by the nested function call.
> Thinking that it might have something to do with the new
> arguments class in
> MX and knowing that this class also stores the named argument values.
"The Arguments scope is special, in that you can treat the scope as
either an array or a structure" (MX docs). This suggests to me there
might be something funny going on behind the scenes. Perhaps it's better
to consider it a read-only scope??
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
