On Mon, Dec 26, 2022 at 09:42:52AM -0800, Michael Stein <m...@zlvfc.com> wrote:
> I'm new to libev and I see now that to support the various backends it
> has to require the watcher be stopped for any modification (other than
> the callback address).
Well, issues can be very hairy, and people's expectations can be all over
the place (for example, even "thread safe" can mean many very different
things), and documenting this so it works always for everybody is a
challenging thing: One could mention all limitations everywhere (good for
prople only referencing the docs), or only in a central place (good
for maintainers and people reading the documentatioon as a tutorial). OR
something in between.
However, re-reeading some parts of the docs, it definitely could be clearer
what was meant by access, and maybe some guidelines are missing. We did go
through the docs and made sure functions clearly are documented as safe to
call on active watchers, and hopefully made it clear that, generally, no
function is safe to call on active/pending watchers, and what to do about
that.
It's probably not optimal, but future releases will make this clearer.
Greetings,
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/mailman/listinfo/libev
