| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
Comments:
<0> godzirra: $kernel->delay( 'event_name', 10, $arg0, $arg1, $arg2, $arg3 ...);
<1> something like {a-z,A-Z,0-9} work?
<2> StylusEater_Work, , it doesn't have to do with dictionary words
<3> godzirra: Basically you want: $kernel->delay_set( MYEVENT, 10 ) ; sub MYEVENT { @blanks=@solved;etc; send(@blanks); $kernel->delay(MYEVENT,10) }
<4> Then why do I need []? (Thats used in the example?)
<4> Or why don't I rather?
<2> StylusEater_Work, \w is any sequence of letters, digits
<1> hrmm
<1> ok
<3> pbelau: Yeah, it's the one that isn't returned.. =]
<0> [] in the first arg? that doesn't seem correct
<4> pravus: I didnt think so either, but thats what the POCo IRC docs say.
<3> godzirra: I duno about the examples.
<4> $irc->delay( [ 'mode' => $channel => '+o' => $dude ], 60 );
<2> buu, no, i mean i need to know what inode it is
<0> if you us [] in the third arg, you will be p***ing your even handler an ARRAYREF
<0> ooh... it wraps ->delay() iirc
<2> buu, or was
<3> pbelau: inode?!
<2> buu, yes, the select in my case can fail because the file was removed
<0> godzirra: that will send an IRC event at the delay you specify
<3> godzirra: Apparently poco-irc has it's own delay magic. We were talking about the poe one. the poco-irc one might be simpler.
<2> i need to check for the condition somehow
<3> godzirra: But it is still clearly documented.
<0> godzirra: and it appears as though it does use an ARRAYREF as the first arg
<3> pbelau: Um. -e ?
<2> buu, how can i check with -e if i have no goddamn idea what file is being selecteed
<0> i think i actually asked for that feature and have never used it...
<4> buu: It doesnt actually show how to supply arguments which is where my initial confusion came in.
<4> Well.. maybe not my initial confusion... but my secondary confusion.
<5> ah, yeah, notice he was using $irc->delay, and we were saying $kernel->delay ... ;)
<3> pbelau: Your question makes no sense. Your basic design is entirely too flawed.
<6> ahh - so this channel is now irc.perl.org #perl now. :)
<6> first #poe, now #perl
<3> godzirra: Why the hell do you even need arguments?
<0> godzirra: arguments to what?
<3> merlyn: Yeah, apparently we are.
<6> welcome to freenode... here's your bot!
<2> buu, a read on a given filehandler fails
<2> i need to know why
<3> merlyn: Heh, yeah.
<4> buu: Because I don't have $hint and $answer declared globally anywhere. They're p***ed as args.
<3> pbelau: TOO BAD.
<7> here's your sign... :-P
<4> pravus: arguments to create_hint
<3> pbelau: An *actual* read will give you an error variable
<0> godzirra: PoCo-IRC's delay() sends the IRC command (not event) you specify at the designated time
<4> Ahh.
<3> pravus: Good point.
<3> merlyn: You aren't even on that #perl
<0> godzirra: perhaps you just want to use the normal POE::Kernel ->delay() ?
<4> Hrm. The doc says events. Not IRC commands. :/
<6> I was formerly
<6> kicked myself off
<3> 'command to post'
<3> Dunno, might be.
<3> merlyn: Why>
<6> 'batteries to full'
<6> 'atomic power to SPEED!'
<3> CANCER to EXCELLENT.
<0> godzirra: well, the example has: [ mode => '#channel' ... ]
<6> DOLLARS to DONUTS
<3> GumbyBRAIN: jerk it
<8> Does it mean it doesn't matter, cause you won't bother reading the specs from the user would have done it in the conditional.
<3> pravus: 'posting events to the component'
<0> godzirra: technically i guess you are sending an event to the PoCo-IRC session... which then sends the command
<3> pravus: Hrm. You probably do want the kernel delay.
<3> godzirra: So anyway, use delay, send an event, catch the event, send a hint.
<3> godzirra: Noet that you need to keep track of the delay ID so you can remove it when the hint is solved.
<5> and cancel the delayed event when something else happens
<4> Is this correct? my $hint_id = POE::Kernel->delay_set( 'create_hint', 10, $answer, $hint );
<6> then put that in the heap so you can find it
<6> in create_hint
<6> and anywhere you wanna kill it
<4> Yeah, I'm trying to figure out how to find the heap. I don't believe its declared globally in my setup.
<5> why do you need the id? can't just run kernel->delay('creat_hint') to unset the delayed event?
<6> is that possible?
<4> dkr: The new methods only list delay_set, not delay.
<5> that's how I do it for timeout events
<4> Is delay still available?
<6> it would seem to me that because it doesn't explictly say it will kill it, that it would create it with 0 seconds to go
<6> oh - excuse me
<4> Hrm. My hint is never happening.
<6> the delay EVENT_NAME
<4> if I use delay, or delay_set.
<5> I was just looking at my odl code, not the docs, :) if ($kernel->delay("authorization_timeout")) { #clear auth timeout
<6> damn - I could use that when I get back to $client[0]
<9> testing
<5> maybe it worked for me by accident, I better double check, ;)
<6> I was trying to figure out how to withdraw my heartbeat
<6> no - it's documented
<6> ... you can always get the
<6> ... delay EVENT_NAME
<6> (forget the mispaste)
<6> ... To clear existing timed events for 'do_the_other_thing' without set-
<6> ting a new delay:
<6> argh
<6> bleh - forget the really bad mispates. :)
<10> How "strong" is __END__ ?
<6> it's really strong
<10> Does everything following it not get executed?
<6> you can smell it from a mile away
<5> chuck norris strong
<6> *nearly* chuck norris
<6> chuck norris can cause stuff after __END__ to be executed. :)
<6> __END__ stops the compilation, and leaves the DATA filehandle there.
<4> So I'm still not sure why my creatE_hint isnt running.
<11> it's only rambo strong then
<9> what's the diff between __END__ and __DATA__
<6> you could always say eval join "", <DATA> and execute everything else. :)
<4> my $hint_id = POE::Kernel->delay( 'create_hint', 10, $answer, $hint );
<4> That doesnt seem to work... with delay or delay_set
<6> __DATA__ makes $currentpackage::DATA
<6> __END__ makes main::DATA
<9> ah
<5> godzirra: did you ***ign an event handler for the 'create_hint' event?
<4> Yup.
<4> in my create for my POE::Session I have create_hint => \&create_hint,
<4> Hmm.. my bot timed out after setting the delay.
<4> 3 minutes after it.
<4> the timer on the delay was only 10 seconds.
<12> hmmm...POE is interesting looking.
<4> So yeah.. not entirely sure whats going on with that delay.
<5> I use the oo method: $kernel->delay()
Return to
#perl
or
Go to some related
logs:
#perl
#debian
APTGART NVidia
+ubuntu +sudo pppoeconf +pppoe +concetrator
kentaur porn
gentoo VT1211
#asm
#asm
#math
32bit ubuntu xlocale
|
|