Re: Debugging memory usage

2005-12-29 Thread Dmitri Tikhonov
Dave C wrote: Is there a recommended "Best Practices" for debugging memory consumption in POE? I ask because, while doing some testing with a script that tails maillogs, I'm noticing that the resident RAM usage is increasing about 1MB per hour and never freed. Any help or suggestions would be a

Re: Signal delivery in POE and time warp.

2003-09-02 Thread Dmitri Tikhonov
On Mon, 1 Sep 2003, Peter Chen wrote: > > Wouldn't it be nice if such monotonic clock source was in ANSI C? What > > would you say if I wrote an experimental module for monotonic clock > > (only > > for Linux for now, based on uptime), and it would be an option to > > POE::Kernel to either use

Re: Signal delivery in POE and time warp.

2003-08-29 Thread Dmitri Tikhonov
On Fri, Aug 29, 2003 at 01:05:55AM -0400, Rocco Caputo wrote: > On Thu, Aug 28, 2003 at 05:27:22PM -0400, Dmitri Tikhonov wrote: > > I was looking at POE::Kernel again to try to figure out this problem, and > > then I re-visited this thread. It hit me that because of semantic

RE: Signal delivery in POE and time warp.

2003-08-28 Thread Dmitri Tikhonov
I was looking at POE::Kernel again to try to figure out this problem, and then I re-visited this thread. It hit me that because of semantic differences between alarm() and delay(), POE::Kernel would have to use _two_ time scales instead of one it uses right now (system time). In an event loop, de

Re: POE::Wheel::Run resource leak?

2003-03-24 Thread Dmitri Tikhonov
I think that your interpreter is having problems freeing memory associated with closures. I ran into this before, and what I had to do is to patch POE so that POE::Wheel::Run accepts arguments. Check it out here: http://rt.cpan.org/NoAuth/Bug.html?id=1783 (the patch is against version 0.22, but

Re: naming quandary

2002-12-16 Thread Dmitri Tikhonov
On Mon, 16 Dec 2002, Erick Calder wrote: > also, these names are getting rather long... would PoCo::Detect::Fs, or > PoCo::Detect::Path be better? I think PoCo::Detect::Fs looks prettier. To make it prettier yet, use caps: PoCo::Detect::FS. - Dmitri.

Re: http://poe.perl.org/

2002-12-16 Thread Dmitri Tikhonov
On 16 Dec 2002, Al Tobey wrote: > err ... what happened here? I'm getting one of those domain-hosing > "portal" sites. > > www.perl.org seems ok, though. > > Is anybody else experiencing this? I get the same thing. Big big eww! - Dmitri.

Re: POE::Wheel::Run add'l functionality.

2002-11-12 Thread Dmitri Tikhonov
On Tue, 12 Nov 2002, Rocco Caputo wrote: > I have forwarded your patch to the task queue at [EMAIL PROTECTED] OK, thanks. How long do those usually take? There are about 20 unfiled items. > I have been recommending > > Program => sub { do_something($abc, $something_else) }, > > which doe

Re: POE::Wheel::Run add'l functionality.

2002-11-12 Thread Dmitri Tikhonov
e of my patch is that one will be able to pass arguments to Program if it is a code ref, and I listed the behavior in my first post: > On Fri, Nov 08, 2002 at 04:23:30PM -0500, Dmitri Tikhonov wrote: > > > > Where Program is a code ref, the behavior will be > > $program

Re: POE::Wheel::Run add'l functionality.

2002-11-08 Thread Dmitri Tikhonov
On Fri, 8 Nov 2002, Dmitri Tikhonov wrote: > > I am thinking of adding extra argument to POE::Wheel::Run's constructor: > > ProgramArgs => [@args], > > > Where Program is a scalar, the behavior will be > exec($prog . ' ' . join(' 

POE::Wheel::Run add'l functionality.

2002-11-08 Thread Dmitri Tikhonov
I am thinking of adding extra argument to POE::Wheel::Run's constructor: ProgramArgs => [@args], Where Program is a scalar, the behavior will be exec($prog . ' ' . join(' ', @$args); Where Program is an array ref, the behavior will be exec(@$prog, @$args); Where Progra