>> > > There are some array functions you can use on >> > > Arguments in MX but not all -- as a matter of >> > > fact, there are array functions which could be >> > > used on the Arguments array in CF 5 that now >> > > can't be used on them in MX (imho this is a >> > > bug), for instance, you can't use arrayprepend, >> > > arrayappend or arrayinsertat on an array in CFMX >> > > (which I had been using for several wrapper >> > > functions until I realized they didn't work in >> > > MX). But ArrayLen() still works. >> > >> > I'm not sure I understand. I've successfully used >> > ArrayAppend on arrays in CFMX - this is part of the >> > Advanced CF Development course curriculum, so I'm >> > pretty sure that it works. I haven't tried to use >> > these functions on the Arguments array, but I >> > wouldn't expect them to work there - it seems that >> > the Arguments scope should logically be read-only >> > to me. >> >> The array wasn't read-only in CF 5 (and isn't read-only >> in CF MX) -- in CF 5 it worked much the way the arguments >> array works in JavaScript ...
> OK. I misread the intent of your original statement a bit, > I guess, in which > you stated that you can't use the array functions on an > array in CFMX. To be > honest, I'm not sure why MM decided to expose the > Arguments scope as both an > array and a structure, either. Did I say that? Must have been a typo. :) It was meant to be "can't use some array functions on the arguments array" -- but then that has to be qualified with "it's not an array anymore ... " <sigh>... If they had written the object such that those few remaining array functions would work on it (the specific implementation wouldn't really matter to me), then I wouldn't care that they'd exposed it as a speciality Java class instead of an array... it's just really frustrating having to tapdance around using the array as an array the way we could with CF 5. And it's possible still that they could fix it moving forward by adding the ability to use those arrayfunctions with the Java class, after all, arraylen() still works. I'm just disappointed that it's been overlooked, and honestly somewhat doubtfull that it will be fixed. ... does anyone on the list know if any of the contents of the submissions to the wish-form are made public? Personally I think it would be really nice to see just what has been suggested in a url-accessible fashion, and have the ability for members of the CF community to "vote" for a given wish-form item by logging in on the MM site, viewing the wishform and hitting a button that says "yes, I think we need this". I think we can largely trust the cf community that people won't be creating bogus MM site logins just to fill the ballot box as it were. Plus -- it might also make the wish-form easier for the folks at MM to manage if they simply sort by votes descending, rather than having to wade through hundreds of individual requests and match up the texts to say "okay, these 3 say roughly the same thing"... s. isaac dealey 954-776-0046 new epoch http://www.turnkey.to lead architect, tapestry cms http://products.turnkey.to tapestry api is opensource http://www.turnkey.to/tapi certified advanced coldfusion 5 developer http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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
