Re: lingo-l object destruction

2001-02-21 Thread Jakob Hede Madsen
At 15:20 +1100 01_02_21, Luke Wigley wrote: if objectP(myCallBackObj) then call(myCallBackMsg, myCallBackObj, myTaskID) end if An even smaller detail: If there is doubt about an objects objectivity ;-) call #myCallBackMsg, [myCallBackObj], myTaskID The list-wrapping avoids

Re: lingo-l object destruction

2001-02-20 Thread Jakob Hede Madsen
At 15:29 +1100 01_02_20, Luke Wigley wrote: A barebones version of the script looks like this property mytimeoutName property myCounter on new (me) myCounter = 0 mytimeoutName = me.string"thread" timeout(mytimeoutName).new(100, #mProcessThread, me) end on mProcessThread (me) if

Re: lingo-l object destruction

2001-02-20 Thread Luke Wigley
Jakob Hede Madsen wrote A small detail here, is that timeout_objects actually send their own reference when making callbacks to their target, so you don't need to store any reference to them, string or directly. Hi Jakob, thanks for pointing that out - I never realised they pass their own

lingo-l object destruction

2001-02-19 Thread Luke Wigley
Hi, I'm trying to track down a small memory leak, and my main culprits at the moment are some small 'utility' objects. These objects create a timeout object (containing the only reference to the object), does some stuff, then forgets the timeout object. A barebones version of the script looks

RE: lingo-l object destruction

2001-02-19 Thread Mark R. Jonkman
Hi Luke Reasoning would dictate that the object should perish when all references to it cease to exist. Since the only reference to the object should be within the timeOut object I'd assume, like you, that if the timeOut object ceases to exist, the object should also cease to exist. However, you

RE: lingo-l object destruction

2001-02-19 Thread Mark R. Jonkman
Hi Is there anyone out there that can explain to me what exactly is that d*#@ BBC mail server's problem. Is there a vbscript equivalent to timeOut or something that it doesn't like. Every time I turn around and discuss timeOut objects I get a nasty note from the BBC that I've just sent them a

Re: lingo-l object destruction

2001-02-19 Thread pranavn
Well Luke, I am not much into the theory of OOPs, but it seems that you are wrong about the object reference being erased when the timeout is forgotten. You will need to assign the object to a variable by using a return statement and explicitly set the variable to void later. The timeout is a

RE: lingo-l object destruction

2001-02-19 Thread pranavn
Boy!!! Thats a relief Mark. And I was going nuts all last week checking my machine for a virus. :-) snip Is there anyone out there that can explain to me what exactly is that d*#@ BBC mail server's problem. Is there a vbscript equivalent to timeOut or something that it doesn't like. Every

RE: lingo-l object destruction

2001-02-19 Thread Mark R. Jonkman
Hi Pranav Well Luke, I am not much into the theory of OOPs, but it seems that you are wrong about the object reference being erased when the timeout is forgotten. You will need to assign the object to a variable by using a return statement and explicitly set the variable to void later.

RE: lingo-l object destruction

2001-02-19 Thread pranavn
Oh boy!! That was some primer for my OOP theory. Thanx Mark. Regards, Pranav [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is

Re: lingo-l object destruction

2001-02-19 Thread Luke Wigley
[EMAIL PROTECTED] wrote I am not much into the theory of OOPs, but it seems that you are wrong about the object reference being erased when the timeout is forgotten. You will need to assign the object to a variable by using a return statement and explicitly set the variable to void later.

Re: lingo-l object destruction

2001-02-19 Thread Luke Wigley
Mark R. Jonkman wrote One thought, I'd try is to stuff a put statement into an exitFrame frame handler within the object to see if the object clears itself... however, it might only indicate that timeOut object was successfully deleted from the timeOut list. Yeah, part of the problem of