Hi all,
I've recently been doing work with the node.js project, and I've been updating
their filesystem module to support a lot more of the functionality that lbeio
provides. I have come across a few cases where libeio doesn't provide something
that may be really useful, these cases are:
-
On Fri, Feb 19, 2010 at 07:14:28PM +0100, Alejandro Mery am...@geeks.cl wrote:
ok, simple test case. (yes, it's only warnings, but they distract a
LOT)
Really, this has nothing to do with libev - you found a buggy warning in your
compiler, report this against your compiler, or switch it off.
On Sat, Feb 20, 2010 at 9:41 AM, Brandon Black blbl...@gmail.com wrote:
I've seen this strict-aliasing issues with libev + gcc 4.4 as well. I
haven't bothered to report it yet simply because I haven't had the
time to sort out exactly what's going on, and whether it's a real
issue that needs
I did look at those strict aliasing warnings a while back. It seemed
to me that they're not bugs.
They're caused by the header declaring structures (specifically ev_*
and ev_watcher) that start with some common elements, casting a
pointer to one to a pointer top the other, and accessing the
