In Railo and CF when you pass this struct into a method as it's
argumentCollection the arguments are accepted in the order of the
struct.
I'm not sure exactly what you mean here. argumentCollections are
matched to the cfargument names by struct key names, not by how the keys
could be iterated in.
Struct
a -> 1
b -> 2
pass as argumentCollection...
Method
argument a
argument b
Matched!
----
Struct
a -> 1
c -> 3
pass as argumentCollection...
Method
argument a
argument b
Only argument "a" is matched
----
If I'm understanding this correctly, you're relying on the key names of
the struct which are "1" and "2" to be matched with arg1 and arg2?
Structs are unordered and relying on the order of the keys in ACF
doesn't work all the time. Right now I think you're relying on
un-intended behavior / action in ACF that is undocumented but then again
I might be missing a key fact.
If you could provide a CFC that illustrates the behavior, I think that
should shed the most light on getting everybody on the same page.
.pjf
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
official manual: http://www.openbluedragon.org/manual/
Ready2Run CFML http://www.openbluedragon.org/openbdjam/
mailing list - http://groups.google.com/group/openbd?hl=en
