in reply to A continually running process

If you can get Glib installed on win32, I would Roll your own Event-loop and use a timer. If you have Tk running with ActiveState, it has timers too. Also see How to implement a timer in perl?. 
#!/usr/bin/perl
use warnings;
use strict;
use Tk;

my $mw = new MainWindow;
$mw->withdraw;

$mw->repeat(1000, \&launch);

MainLoop;

sub launch{
  system( "date" );
}

[download]
I'm not really a human, but I play one on earth CandyGram for Mongo

Replies are listed 'Best First'.
Re^2: A continually running process
by BrowserUk (Patriarch) on Jun 26, 2008 at 13:28 UTC

    Getting Glib installed on Win32 just to obtain a timer would be most perverse.

    All windows programs have message loop accessible and therefore, an event loop and timers, along with a whole plethora of other waitable timers and synchronisation mechanisms.

    Suggesting Glib or Tk in order to avoid disabling buffering on STDOUT is, well, let's just say: overkill.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
      Well you are probably right, however my point was to make becca23 aware of the benefit of using timers rather than sleep..... where or how she gets the timer makes no matter to me. Timers alllow program expansion and/or control, which sleep precludes.
      I'm not really a human, but I play one on earth CandyGram for Mongo
[reply]

In Section Seekers of Perl Wisdom