On Thu, Nov 08, 2007 at 07:01:37PM +0100, Marc Lehmann wrote: > Hi! > > http://data.plan9.de/libev-1.3e.tar.gz > > is the first "release" (on a very low level of release) of the libev event > core, which is a drop-in replacement for libevent, fixing API problems with > a new API while providing libevent compatibility.
Hi, Marc! I tried building Tor against libev to see how well it would work. There are some very cool things in your code design, but I ran into the following issues when I tried to run it. - I got some GCC warnings when building ev.c; I've attached them. - You probably want event.h to include <event_compat.h> inside angle brackets, not inside quotes. - There's no event_active compatibility function defined. I looked around ev.c to try to figure out how to do it, but it looks like I would need to call the static function "event()" in ev.c. Instead, I commented out the code that used it. This breaks some Tor features, so I turned them off. - It looks like the way that fd_event() handles FD events uses an array, anfd, to map fd values to ev_io values. This won't work very will on windows, where sockets aren't 0-indexed and aren't necessarily sequential. Any thoughts on how to get win32.c working? - I needed to include "-lm" and "-lrt" in my libraries to build. This isn't a bug, but it's something other people should know if they want to try this too. Once I did this, stuff seemed to work okay. Other people should try out libev with your existing applications too. If it works, and you don't run into any incompatibilities, that would be a point in favor of dropping something like the current libev core into a future libevent. cheers, -- Nick Mathewson
pgpuUJHMcks8J.pgp
Description: PGP signature
_______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
