Call me crazy, but it if you have a DynAPI.destroy method, wouldn't
you put it in dynapi.js? Why would you put DynAPI.destroy in
dyndocument.js? That doesn't seem logical.
--
// Robert Rainwater
On 1/18/2001, 7:27:18 PM EST, Doug wrote about "[Dynapi-Help] Memory Leak":
> Thank You
> ----- Original Message -----
> From: Jon McLennan
> To: '[EMAIL PROTECTED]'
> Sent: Thursday, January 18, 2001 1:17 PM
> Subject: RE: [Dynapi-Help] Memory Leak
> I would put the DynAPI.destroy function in DynDocument.js.
> -----Original Message-----
> From: Doug Melvin [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 18, 2001 4:07 PM
> To: dynapi-help
> Subject: [Dynapi-Help] Memory Leak
> I am attacking the memory leak issue..
> For starters..
> All objects should have a destroy() method.
> This method would destroy array,strings,objects, ect belonging to this object.
> The destroy method of each object should be called in DynAPI.deleteChild().
> this SHOULD allow ram to actually be cleared.
> Now, I've noticed that in some places obj=null is used rather than delete obj.
> Is there a reason for this?
> I also want to add a DyAPI.destroy() which will try to clear up all objects.
> What file do I add this to? DynLayer.js or DynDocument.js?
> Tell me this and by tomorrow we will have a prototype for DynAPI.destroy().
> Thank You,
> Doug Melvin
> Integrated System Solutions: Design, Development, Implementation and Support
> Creative-Workshop.com
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
