> 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. If we're talking about the same classes (mx/collections/ArrayList.as and org/apache/flex/collections/ArrayList.as), there is no actual difference in how UPDATE events are handled (only different function calls, but they do exactly the same thing). The only differences seem to be:
1) the mx version has a "toJSON()" function 2) addAllAt is quite different, with the mx version being more recent (Carol Frampton committed it against an Adobe ticket SDK-30008) 3) my recent fix for FLEX-34885[1], which I only applied on the mx side for now, till I get my head round this duplication. So to reiterate Gareth's question: do we know why we have the flex/collections version of the ArrayList class (given that Mike said he doesn't know either, and pointed to a commit by Carol Frampton)? I just did a search for "flex.collections.ArrayList" and there are no results, implying that this version is never used. Can we delete it? It looks like we wouldn't miss anything useful. [1] https://issues.apache.org/jira/browse/FLEX-34885
