So if the Garbage collector delete classes with no references to them immediately, but waits to do the more expensive check to see if the class has no references from the root, then with your classes that you know will have circular references, would it be a good idea to write a dispose method that does a for in loop on the instance, and deletes everything it can find?
In other words, when you don't need an object, you just delete it, or make all references to it null, but if your object contains an object that has a reference to the original object, then there's still a reference. So you just include a method in the contained classes that delete all their references, and a method in the containing class that does the same thing, so if you do everything right, when you call that method, it takes care of eliminating all it's references, and gets cleaned up more quickly. ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
