[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 08 Jun 2012 18:46:36 +0200
From: John Spencer <maillist-musl@...fooze.de>
To: musl@...ts.openwall.com
CC: Szabolcs Nagy <nsz@...t70.net>, rrt@...d.org
Subject: Re: printf POSIX compliance
On 06/08/2012 05:06 PM, Szabolcs Nagy wrote:
>
> i've just checked m4 and it uses freadseek and closein
>
> both functions are from gnulib and depend on freadahead
>
> so m4 will use freadahead independently of the printf issue
>
closein.c reads:
"
Most programs can get by with close_stdout. close_stdin is only
needed when a program wants to guarantee that partially read input
from seekable stdin is not consumed, for any subsequent clients.
For example, POSIX requires that these two commands behave alike:
(sed -ne 1q; cat) < file
tail -n 1 file
"
this is bogus, according to Rich:
"all files are closed when a process terminates normally/calls exit.
if you want to report write failures, just fflush(stdout) before exit
and check the return value"
to make this stuff happening, they manipulate the libc-internal FILE
struct, which is even more bogus.
gnulib is simply a huge pile of junk...
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
