> Check out the technotes at MACR. > > I think it has a memory leak, I think it may crash otherwise, > and basically MACR says "well, use the Flash one".
No, not quite. To start, yes, there is a memory leak in the XML parser Xtra that's documented in a tech note: <http://www.macromedia.com/go/16805> When I was asked the question "how do I avoid the memory leak?" I answered by indicating that folks should use the Flash XML parsing abilities as you simply can't prevent the XML Xtra's memory leak, you can only minimize it. If you ask me "can this Xtra be used in any way such that the memory leak isn't a problem?" then I can answer "yes". The issue is that each time you call parseString you leak memory, the amount lost is proportional to the size of the string being parsed. If your movie parses a string once (for initializing as an example) then go ahead and use the XML parser Xtra, if instead your project does lots of repeated parsing then we get into a more gray area and you have to make some careful decisions. How much parsing? How often? How large are the strings you'll parse? etc. The only time I have recall having said "use the Flash XML parsing abilities" was in replying folks asking how to avoid the memory leak altogether. But you still can strategize on how to use the XML parser Xtra while minimizing the memory leak so it's not a problem, but that comes on a per-project evaluation of how you'll use it. Have you heard from another source that you should always and definitively use the Flash XML parsing abilities and completely forego using the XML parsing Xtra? Now, if I can get some dev time focused on fixing the memory leak we can get over this hump... ;) Cheers, Tom Higgins Product Specialist - Director Team Macromedia ... [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
