On Sun, Feb 03, 2008 at 07:47:12PM -0700, Tony Arcieri <[EMAIL PROTECTED]>
wrote:
> > Sweet, I'll be checking it out this weekend
> >
>
> One thing: the docs show ev_async_send() taking one argument (the ev_async
> struct) which makes sense. But in the CVS version, it takes both the loop
> and the ev_async struct. Shouldn't the ev_async struct store the loop it
> was started on?
That would be a pretty strong deviation from the API (_all_ other
functions take the loop argument and no watcher stores its loop), so I guess
it would be rather confusing to people.
--
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
