[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: critique of gnulib - stdioext
From: |
Bruno Haible |
Subject: |
Re: critique of gnulib - stdioext |
Date: |
Sun, 08 Sep 2019 19:20:58 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-159-generic; KDE/5.18.0; x86_64; ; ) |
Jonas Termansen wrote:
> It's been a while since I looked at the stdio-ext functions, although
> I'm not really sure why they need to exist. At least there is a way to
> satisfy gnulib.
These functions exist
a) to enable important functionality that has been forgotten by the ISO C
standards authors, e.g.
- fseterr (why should a custom/extended printf implementation not be
able to set the error indicator of a stream?)
- fpending (needed when, at the end of a program, we want to flush
stdout in a safe way, but without introducing unneeded system calls).
b) as an optimization, so that e.g. GNU m4 does not need to copy the contents
of the FILE buffers into its own buffers, but can already do searches
for newlines and parentheses directly in the FILE buffers.
Bruno
Re: critique of gnulib - stdioext,
Bruno Haible <=
Re: critique of gnulib - malloc wrapper, Bruno Haible, 2019/09/08
Re: critique of gnulib - disabling workarounds, Bruno Haible, 2019/09/08