From: Mark P. <mar...@hi...> - 2001-02-21 14:35:52
|
From "Javascript : The Definitive Guide - 3rd Edition, Flannagan - O'Reilly" "Note that delete affects only property values, not objects referred to by those properties" also "If you are a C++ programmer, note that the delete operator in JS in nothing like the delete operator in C++. In JS, memory deallocation is handled automatically by garbage collection, and you never have to worry about explicitly freeing up memory." From this can we establish that we cannot rely on delete to free memory reliably ??? Does this also mean that we'd have to iterate through sub-objects deleting them? Perhaps some kind of destroy() method ??? Pascal wrote: > so: > > myLayer = new DynLayer > > delete myLayer > > destroys it completely? (or do we have to delete every object created within > the dynlayer object ?) > > Pascal Bestebroer (pb...@oi...) > Software ontwikkelaar > Oberon Informatiesystemen b.v. > http://www.oibv.com > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens Eytan > > Heidingsfeld > > Verzonden: woensdag 21 februari 2001 14:20 > > Aan: Dynapi-Dev > > Onderwerp: [Dynapi-Dev] Continuing Freeing memory > > > > > > Amazing news flash: > > Thanx to Bradford Maness and the delete command in JS I found > > that if you > > delete objects(repeating objects not elements) in IE memory is freed. > > > > 8an > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev |