Append(aa as Object)
Append an AssociativeArray to this one.
Hi Enterr, I filed a bug on the last part of your posting (the lack of type checking) the day after you initially posted it.
Documentation - I can point that out to the documentation people.
a = [1,2,3]a) print 1 2 3 4
Hi, as you noted "b" prevails. That would be the standard behavior that I don't think we would want to change. Of course, its software, so everything can change if someone decides to make it so as a matter of policy, or accidentally breaks something...
I will give you a reason so my question does not seem capricious: i intend to use this for (home-grown, class-less) object inheritance, so that new methods override parent's existing methods.
"ifAssociativeArray.Append(aa as Object)" wrote:So it is behavior (B), the new AA overrides old AA content in case of overlapping keys. As any experienced developer would expect but now is in the RTFM and can be relied upon.
... If any key in aa are already associated with a value in this AssociativeArray, the current value is discarded and is replaced with the value in aa.