Line-buffered EV_READ

Marc Lehmann schmorp at
Wed Jul 28 03:16:01 CEST 2010

On Tue, Jul 27, 2010 at 11:14:47PM +0200, Luca Béla Palkovics <luca.bela.palkovics at> wrote:
> I had a own "select-routine" with sockets and wanted to upgrade my code
> to use libev.
> But libev just gives me a signal when the socket gets a '\n', is this
> normal ?

Since libev doesn't give you any data or does any buffering, this is just
bullshit - please don't make up obviously wrong statements like that, that's
not helpful.

If you have a bug in your code somewhere, it's much better to explain
the behaviour you are seeing, the behaviour you are expecting, and an
explanation how both differ.

Giving code excerpts might help as well.

> Is there a way to change this behaviour ?

The behvaiour doesn't exist in any libev version - there is no way to even
implement this behaviour even if wanted.

Most likely, the sender only sends data after \n, or you use a
line-buffered tty.

Both have nothing to do with libev, but would be bugs in your code (or the
sender side).

                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_    
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at
      -=====/_/_//_/\_,_/ /_/\_\

More information about the libev mailing list