This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH][BZ #6885] Clarify description of __freading and__fwriting
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: Rich Felker <dalias at aerifal dot cx>, libc-alpha at sourceware dot org
- Date: Wed, 9 Jan 2013 17:07:57 -0800 (PST)
- Subject: Re: [PATCH][BZ #6885] Clarify description of __freading and__fwriting
- References: <20121213130709.GA29577@spoyarek.pnq.redhat.com><20121213152832.D6B8F2C0C3@topped-with-meat.com><20121213194658.GF20323@brightrain.aerifal.cx><20121214181639.GB8938@spoyarek.pnq.redhat.com>
> +The @code{__freading} and @code{__fwriting} functions exist primarily for use
> +by gnulib and for other legacy software. Their use in new programs is not
> +recommended.
If we were to mention gnulib it would belong in @file or something. But I
don't think we should use wording like this. If we want to discourage use
of an interface, the the manual should describe why it's suspect to use it
and what patterns we recommend instead that make its use unnecessary.