Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>Very minor stuff.
Has anyone built Event against bleadperl with USE_PERLIO ?
--
Nick Ing-Simmons
Very minor stuff.
--
May the best description of competition prevail.
(via, but not speaking for Deutsche Bank)
# This is a patch for Event-0.80 to update it to Event-0.81
#
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this
On Wed, Jan 31, 2001 at 12:01:07PM -0500, [EMAIL PROTECTED] wrote:
> JNP> Do you $idle->min(0) ?
>
> nope.
Please do! The default is *not* zero! (It is 0.01 sec.)
> i wasn't sure if that was what i needed. i need only one triggered
> event perl plain/idle event. i would have to cancel each
> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
JNP> Do you $idle->min(0) ?
nope. i wasn't sure if that was what i needed. i need only one triggered
event perl plain/idle event. i would have to cancel each idle event as
it is triggered which is ok.
JNP> Please calm down, i'm s
On Wed, Jan 31, 2001 at 07:13:43AM -0500, "Horsley Tom" wrote:
> > Too bad it can only wait on 32 or 64 handles, eh?
> That depends on what MAXIMUM_WAIT_OBJECTS is defined in the MS headers.
> If it really is as small as 64, that seems a little on the pitiful
> side, but I've never run into a prob
On Wed, Jan 31, 2001 at 12:26:14AM -0500, [EMAIL PROTECTED] wrote:
> JNP> i think the fix is trivial. Please confirm.
>
> this fixes the test bug.
Good. i'll upload 0.81 shortly.
> but i still notice a delay in dispatching idle
> events. maybe i am not thinking about them the right way. my
> Too bad it can only wait on 32 or 64 handles, eh?
That depends on what MAXIMUM_WAIT_OBJECTS is defined in the MS headers.
If it really is as small as 64, that seems a little on the pitiful
side, but I've never run into a problem with it.
> Also it doesn't work for pipes, and if memory serves,
