You will get inconsistent results because internally, the HashMap utilizes a Dictionary object, thus when you invoke HashMapA.getEntries(); the underlying algorithm uses a “for in” loop, which when used to iterate over an Object or Dictionary the order of the results returned are not guaranteed.

Best,
Eric

errr, i can’t post my for-loop properly

for (var i:int=0; i ” + i + ” ” + mapEntry.key + ” ” + tmpListLen);
}

Then i do:

var iList:IList = HashMapA.getEntries();
var iListLen:int = iList.length;
var mapEntry:HashMapEntry = null;

var tmpList:IList = null;
var HashMapB:HashMap = null;
var tmpListLen:int = 0;

for (var i:int=0; i ” + i + ” ” + mapEntry.key + ” ” + tmpListLen);
}

If you run this code repeatedly, you will notice that tmpListLen yields inconsistent results.

Small problem…

If I do something like mymap.put(”hello”, null) and then mymap.contains(”hello”), it returns false. This is because for “contains()” you implemented it by checking the value in the dictionary. Is it possible to change this so that contains() tests for the existing of the key rather than the null-ness of the value???

Would hasOwnProperty() do this???

Thanks,
Eric

I agree, for the most part these are common APIs one would expect to be included in the framework. The only reason I can think of as to why they are not included is to allow ActionScript 3 to align with the ECMA-262 edition 4 standard - which in many ways is very limiting.

- Eric

{Maz}