> I will fix the bug soon. However, your fix does not delete the
> object, but the array element.
As I understand it, delete doesn't delete an object but cuts the
variable (or the attribute) and therefore the reference out of the
namescape.
> I believe this would cause a memory
> problems.
That depends on whether local variables get garbage collected after
gone out of scope. I don't think that browsers will have a problem
with this.
But you can still assign null instead of deleting.
__
c.del()
this.children[i] = this.children[l-1];
this.children[l-1] = null;
this.children.length--;
c = null // instead of delete c
__
This would work for Netscape.
Stephan
PS: Didn't want Jeff Greenberg to write a tutorial about memory
optimization?
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
