Re: bin/12852: Non-standard behavior of fread(3)

1999-07-29 Thread Sheldon Hearn
On Wed, 28 Jul 1999 20:13:18 +0200, Robert Nordier wrote: > There's no question this needs changing. An ISO example actually > reads along the lines of: The question, though, is whether it needs changing _now_, or whether this'll break a number of critical utilities that rely on the broken beh

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-29 Thread Sheldon Hearn
On Wed, 28 Jul 1999 20:13:18 +0200, Robert Nordier wrote: > There's no question this needs changing. An ISO example actually > reads along the lines of: The question, though, is whether it needs changing _now_, or whether this'll break a number of critical utilities that rely on the broken be

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-28 Thread Robert Nordier
Sheldon Hearn wrote: > Could someone have a look at the patch proposed on PR 12852? I > understand the motivation, since it seems reasonable to me that ferror() > should return EBADF after an attempt to read from stdout. At the moment, > ferror() returns 0 after an attempt to read from stdout.

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-28 Thread Robert Nordier
Sheldon Hearn wrote: > Could someone have a look at the patch proposed on PR 12852? I > understand the motivation, since it seems reasonable to me that ferror() > should return EBADF after an attempt to read from stdout. At the moment, > ferror() returns 0 after an attempt to read from stdout.

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-28 Thread Sheldon Hearn
Hi folks, Could someone have a look at the patch proposed on PR 12852? I understand the motivation, since it seems reasonable to me that ferror() should return EBADF after an attempt to read from stdout. At the moment, ferror() returns 0 after an attempt to read from stdout. Thanks, Sheldon. T

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-28 Thread Sheldon Hearn
Hi folks, Could someone have a look at the patch proposed on PR 12852? I understand the motivation, since it seems reasonable to me that ferror() should return EBADF after an attempt to read from stdout. At the moment, ferror() returns 0 after an attempt to read from stdout. Thanks, Sheldon.