[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: yesno module consumes too much input
From: |
Jim Meyering |
Subject: |
Re: yesno module consumes too much input |
Date: |
Sat, 18 Aug 2007 01:03:03 +0200 |
Paul Eggert <address@hidden> wrote:
...
> My kneejerk reaction is that a modified 'closein' is a better way to
> go here. That is, the affected programs (and there are not that many
> of them) should invoke close_stdin if they have attempted to read
> anything from stdin and have not read end-of-file.
I've been rethinking my position here, too.
Another reason to prefer something like closein is
the gnulib philosophy of penalizing only losing systems.
It's a shame that modern glibc is in the "losing" camp, on this.
Re: yesno module consumes too much input, Jim Meyering, 2007/08/17
Re: yesno module consumes too much input, Paul Eggert, 2007/08/17
- Re: yesno module consumes too much input,
Jim Meyering <=
- Re: yesno module consumes too much input, Eric Blake-1, 2007/08/17
- Re: yesno module consumes too much input, Paul Eggert, 2007/08/17
- Re: yesno module consumes too much input, Eric Blake, 2007/08/18
- Re: yesno module consumes too much input, Bruno Haible, 2007/08/18
- Re: yesno module consumes too much input, Eric Blake, 2007/08/18
- Re: yesno module consumes too much input, James Youngman, 2007/08/18
- Re: yesno module consumes too much input, Bruno Haible, 2007/08/18
- Re: yesno module consumes too much input, Eric Blake, 2007/08/18
- Re: yesno module consumes too much input, Jim Meyering, 2007/08/19
- Re: yesno module consumes too much input, Eric Blake, 2007/08/19