>> Besides, I'm not fooling with any 3rd party workarounds, not with E4X on the way.
this has been around for ages...add to this that e4x is currently in alpha and slow, and the fact that xpath is a w3c spec and even macromedia implement a much thinner version of this in F7 then this statement sounds a bit absurd you will find xpath is very slow on large data sets, and writng certain types of queries make it even slower. i would really consider using a differant format (excel can export cvs, you can parse that much much faster). we tend to use xpath everywhere, check where the bottlenecks are and rewrite those parsing routines using node.firstSibling type access where needed. -- j:pn _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
