Re: Weirdness in comm(1)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 28 Nov 2009 18:18:56 +0100
    From:        Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
    Message-ID:  <20091128171856.GA10358%britannica.bec.de@localhost>

  | Avoids the locking overhead for each character.

Yes, that's what I expected to be the reason - but that could remain
just by doing like the (real, in current) getline() does and locking
outside the loop.

  | The application here is single threaded and the program I use it for too.

They are now - but that's not something that you want to rely upon, and
it appeared as if you were suggesting that your function could be generally
used (in more than just comm) in order to allow geline() to be used on
older releases.

  | That doesn't mean they might not pull in pthread somehow...

I doubt that linking the library would hurt, only actually creating
threads, which is less likely by accident - but someone has to remember
that even though getline() is thread safe (the real one), this replacement
version isn't, in case of other upgrades to applications that use it.

kre