I just looked quickly at the differences. It appears that the second ArrayList has different update event logic so it may be that it was safer to create a different ArrayList so we wouldn’t have to worry about backward compatibility issues.
-Alex On 5/13/15, 2:31 PM, "Gareth Smith" <garethdanielsm...@gmail.com> wrote: >It looks like the second ArrayList was introduced by Justin Mclean in >this commit: > >https://github.com/apache/flex-sdk/commit/621e4debe8cd46e9ec5a197256dc2b6e >32fc47c3 > >I can't figure out why it was included though. Justin? > >Thanks >Gareth > >On 10/05/15 11:29, Gareth Smith wrote: >> Hi, >> >> I am putting together a patch for ArrayList to support square-bracket >> indexing and for-each loops, see: >> https://issues.apache.org/jira/browse/FLEX-15159 >> >> I am confused by the existence of not one, but two ArrayList classes: >> the "original" one at mx.collections.ArrayList and another one at >> org.apache.flex.collections.ArrayList. >> >> Why are there two classes? Looking at their diff, I would guess that >> mx.collections.ArrayList is newer: it has some additional >> optimisations, and an additional toJSON() method. >> >> I could patch both classes, but I would rather not introduce more >> duplication that might become a maintenance burden along the line. >> >> Thanks >> Gareth >
