Uri,
I have not done extensive testing with it. But from the little that I did
do it seemed to work. I have not noticed any problems with it. I am a
little concerned if a signal comes in between the end of the loop and the
loop restarting.
The work around is as follows:
1. Prior to the loop, set up a timer event:
Event->timer(interval => 5, cb => sub{unloop;});
This example shows a 5 second timer event. However, I'm using 60 seconds
now. Then around the loop do the following:
while (1) { Event::loop; };
If you ever need to truly end the loop then you will have to add some
additionally checking so you can get out of the while loop. I'm not happy
with this solution. It is clearly a kludge. However, the powers the be
seem happy enough for now with this work around.
Brad
-----Original Message-----
From: Uri Guttman [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 12:03 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: leak fixed?
>>>>> "BB" == Bradley Brahms <[EMAIL PROTECTED]> writes:
BB> as far as I know the leak has not been fixed. The application I
BB> was working on uses the method you described. For now, that was
BB> satisfactory for my customer. Its a hack, but it appears to work.
can you post that workaround again? are you sure it doesn't leak and has
the same functionality as the regular main_loop call?
thanx,
uri
--
Uri Guttman ------ [EMAIL PROTECTED] --------
http://www.stemsystems.com
--- Boston Perl Classes ---- July 1-3 ----
http://stemsystems.com/class/ ----
----- Stem and Perl Development, Systems Architecture, Design and
Coding ----
Search or Offer Perl Jobs ----------------------------
http://jobs.perl.org
