> The ev.pod documentation notes that: "Due to some design glitches inside
> libev, child watchers will always be handled at maximum priority (their
> priority is set to EV_MAXPRI by libev)"
And additionally, no, you can't rely on the order of watcher invocations to
be related to their starting order.
You can work around the problem if missing watcher priorities for child
watchers by starting check (or even prepare) watchers with the respective
priorities inside the child watcher(s).
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
