Re^2: Bot::BasicBot forkit

Thanks, I'll steal the idea, but this still leaves me a couple of questions:

I understand I can only have one tick that schedules the next and so on, this makes it pretty complicated if I want to have multiple tasks;
I am still at a loss regarding debugging this. I don't think the debugger will be as simple with POE in the mix. I'll try, but logging to stderr would still be nice.

Comment on Re^2: Bot::BasicBot forkit - help needed

Replies are listed 'Best First'.
Re^3: Bot::BasicBot forkit - help needed by moritz (Cardinal) on Jul 20, 2009 at 17:31 UTC
You could try to dig more into the POE stuff - I'm sure timers aren't that hard. but logging to stderr would still be nice Nothing prevents you from using warn or `print STERR $msg;` to achieve that.	[reply] [d/l]
Re^3: Bot::BasicBot forkit - help needed by neilwatson (Priest) on Jun 26, 2015 at 15:16 UTC
Did you ever come up with a way to schedule multiple tasks? I was thinking of using tick to fork each task each with its own wait time. I think there is some logic problem there, but it's a start. `# psuedo sub tick { # stuff.... $self->forkit( run => \&task1, channel => $channel, arguments => [ $arg1, 20 ] ); # Where second arg is for a sleep. $self->forkit( run => \&task2, channel => $channel, arguments => [ $arg1, 40 ] ); # Where second arg is for a sleep.` [download] Neil Watson watson-wilson.ca	[reply] [d/l]