> So do you think there's a difference between delete c, and c=null as far as
> memory-leaking is concerned?

To restate my postition: I don't think there's a difference concerning
memory-leaking.

> 
> If not, simply changing to c=null might help fix this bug:
> Or will changing the order like Stephan suggested harm anything?
> see:
> http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/msg03569.html

Please forget my old code fix.
I would just replace delete c with c = null:
__
c.del()
this.children[i] = this.children[l-1];
this.children[l-1] = null;
this.children.length--;
c = null // instead of delete c
__

> This bug has been mentioned before too, but seems only to happen to
> some-people sometimes. (especially on Linux I think)

Look at:
http://www.mail-archive.com/dynapi-help%40lists.sourceforge.net/msg03236.html

I can confirm the error for Netscape 4.7 on Win2k.

Stephan


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to