watching for new files: libevent vs. libev

Mikhail T. mi+thun at
Fri Apr 5 19:57:49 CEST 2013

On 05.04.2013 13:47, Marc Lehmann wrote:
> I do care, but since the only place where this warning can be fixed is in the
> compiler, caring is not enough.
> If you disagree with that, you had ample time to explain what the problem
> is, or how you think it could be fixed.
Compiler warning is THE problem, and blaming the compiler is just funny. Even if 
compiler was at fault in a particular case, the supposedly spurious warning 
should be quieted down so that other warnings will be noticed the second they 

So, yes, I do disagree. I've already spent some time explaining, as you point 
out, but because libev is not doing what I need, I will not be using it (until 
it improves considerably), so I will certainly not be spending any /more/ time 
explaining, what to me is perfectly obvious already.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the libev mailing list