Andy Green writes:
> Libuv seems to manage it just fine.
libuv used to depend on libev, so that's no surprise. It wouldn't do for
libuv to conflict it's own dependency ...
> it's not going to change no matter what I say.
That's probably true: Even if you had a convincing use case for including
l
Hi!
Disclaimer: I'm not a libev developer. Just following this list as a
regular user.
Andy Green writes:
> I'm proposing libevent and libev stop defining the same symbols to
> different values and conflicting, the same way libev and libuv have
> clean namespaces that don't conflict. It's quite b
Andy Green writes:
> For downstream maintainers like me whose users wish to be able to use
> both, and where distro consumers should be able to tick all the boxes
> and choose at runtime, are there any ideas what can be done to improve
> the situation?
It might be a good idea to support selecti
Chris Galas writes:
> I've come upon a strange issue.
>
> I'm reading data from a USB serial port on Linux, using separate reader
> and writer ev_io watchers. Commands (bytes) are written to the file
> descriptor in a write call back and bytes are read back on a read call
> back. This works for ab
