I think I missed a beat here. I just noticed a reference to a post I wrote about E4X in a reply.
What I meant about losing speed was having to use AS2 to use XPath. I didn't know there was an AS3 implementation. I see the value of using XPath in AS3 if you're used to it but I'm not sure why you'd use XPath instead of the native E4X if you're just starting out. I haven't done a side-by-side comparison. There may be superior features in XPath and coding taste and comfort is certainly important. As for custom classes being slower than Player-native classes, that's probably true but I can't imagine that being a factor in parsing XML. That's optimization on a level that is too much for me to bother with. This boils down to sticking with XPath if you're good at that and feel it offers what the native implementation, and either using E4X or comparing features to choose a preference between the two if you're learning from scratch. _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
