I'm not Jordi, and he knows it!
I think it's more important to assure you clean-up and kill any circular
references. Then it doesn't matter the collector will clean it "when it
wants".
If it has "live" references setting it to anything (null,delete,pascalize)
won't motivate a clean-up.
Raymond "the rock" Smith
AKA DS
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Stephan
Tolksdorf
Sent: Wednesday, June 06, 2001 2:50 AM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Memory question
Jordi Ministral wrote:
> But make sure you specifically remove all references to browser objects
> otherwise it will leak. That's what I found out when I was removing the
> memory leaks from the API.
(I'm new to this list...)
You seem to have some experiences with memory leaks in JavaScript.
When should one use object = null and when should one use delete
object? Just curious...
Stephan
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.256 / Virus Database: 129 - Release Date: 5/31/2001
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.256 / Virus Database: 129 - Release Date: 5/31/2001
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
