What is the point of a class (one that is instantiated and used via composition within another class) having a destructor?
Shouldn't the class that composites the other class (let's say a parent class compositing a sub class) just be able to remove all references to sub class and then it will be garbage collected (making sure nowhere else in the application makes reference to the sub class). And further more, why is there no way to flag an object for garbage collection and then force the garbage collector to dispose of the class? Any thoughts on this? Thanks. S0 F1. _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
