On Mon, Feb 22, 2016 at 04:13:07PM +0200, Alex Efros
wrote:
> Okay, that makes sense, thanks.
>
> If it works this way (because of internal libev watchers), then I see
> possible use cases for EV::run(0) and EV::run(RUN_NOWAIT), but can't
> imagine use cases for RUN_ONCE. Are there some examples
Hi!
On Thu, Feb 18, 2016 at 12:51:19PM +0100, Marc Lehmann wrote:
> How do you know there are no other (for example internal) event watchers?
[cut]
> Well, libev cannot really know which events you are waiting for and
> instead returns after any single event. Note that using RUN_ONCE to wait
> for
On Mon, Feb 15, 2016 at 02:02:34PM +0200, Alex Efros
wrote:
> On Mon, Feb 15, 2016 at 12:25:19PM +0100, Marc Lehmann wrote:
> > If I run your script, then the reason the timer isn't invoked instantly
> > is simply because it hasn't elapsed yet - try with delay -1 for example,
> > then it will be
Hi!
On Mon, Feb 15, 2016 at 12:25:19PM +0100, Marc Lehmann wrote:
> I'm not quite sure what the problem is - RUN_ONCE doesn't wait for
> specific events, it simply runs the event loop once, and it seems to work as
> it should in your example.
>
> If I run your script, then the reason the timer is
On Sun, Feb 14, 2016 at 06:15:39PM +0200, Alex Efros
wrote:
> The example is in Perl, but I suppose issue is with libev, not EV.
> EV-4.03 doesn't have this issue, EV-4.10 to 4.22 have this issue.
> It may be related to improvement for low resolution clock mentioned in
> this list for 4.10 (May 2
Hi!
The example is in Perl, but I suppose issue is with libev, not EV.
EV-4.03 doesn't have this issue, EV-4.10 to 4.22 have this issue.
It may be related to improvement for low resolution clock mentioned in
this list for 4.10 (May 2011).
Problem is: timer for < 1sec doesn't invoked by first RUN_
