Query: io::async::timer::absolute
OS: debian
Section: 3pm
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
IO::Async::Timer::Absolute(3pm) User Contributed Perl Documentation IO::Async::Timer::Absolute(3pm)NAME"IO::Async::Timer::Absolute" - event callback at a fixed future timeSYNOPSISuse IO::Async::Timer::Absolute; use POSIX qw( mktime ); use IO::Async::Loop; my $loop = IO::Async::Loop->new; my @time = gmtime; my $timer = IO::Async::Timer::Absolute->new( time => mktime( 0, 0, 0, $time[4]+1, $time[5], $time[6] ), on_expire => sub { print "It's midnight "; $loop->stop; }, ); $loop->add( $timer ); $loop->run;DESCRIPTIONThis subclass of IO::Async::Timer implements one-shot events at a fixed time in the future. The object waits for a given timestamp, and invokes its callback at that point in the future. For a "Timer" object that waits for a delay relative to the time it is started, see instead IO::Async::Timer::Countdown.EVENTSThe following events are invoked, either using subclass methods or CODE references in parameters: on_expire Invoked when the timer expires.PARAMETERSThe following named parameters may be passed to "new" or "configure": on_expire => CODE CODE reference for the "on_expire" event. time => NUM The epoch time at which the timer will expire. Once constructed, the timer object will need to be added to the "Loop" before it will work. Unlike other timers, it does not make sense to "start" this object, because its expiry time is absolute, and not relative to the time it is started.AUTHORPaul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Timer::Absolute(3pm)
Similar Topics in the Unix Linux Community |
---|
(Linux Shell Script) Simulate Bomb Timer |
Loop difficulty |
Loop with Find—damn spaces! |
Loop to read parameters and stop |
Loop with command line arguments |