push_read bug on linux?

Marc Lehmann schmorp at schmorp.de
Sat Sep 18 20:29:02 CEST 2010


On Sat, Sep 18, 2010 at 12:02:29PM +0200, Zsbán Ambrus <ambrus at math.bme.hu> wrote:
> On Sat, Sep 18, 2010 at 9:42 AM, Marc Lehmann <schmorp at schmorp.de> wrote:
> > Since for some reason people keep coming up with this nonsense without
> > trying to understand non-blocking operaitons or googling a bit (or check
> > the mailinglist...), the next release of AnyEvent will actively check for
> > this user error, btw.
> 
> By this, do you mean that AnyEvent will raise an exception if you try
> to watch when a regular file is ready,

with AnyEvent::Strict, yes, without it, you get undefined behaviour as
before.

with AnyEvent::Handle, you will always get an error if you pass an
unsuitable handle to it.

> or that AnyEvent will pretend that regular files are always ready to
> read and write?

While possible, that would incur a major speed penalty for something which
is essentially a programmer error.

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\



More information about the anyevent mailing list