From: Jonny Grant <jg@jguk.org>
To: mtk.manpages@gmail.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: cfree
Date: Wed, 24 Jun 2020 15:46:07 +0100 [thread overview]
Message-ID: <3e87db0e-f7e2-d47f-2a91-e110ffaf343e@jguk.org> (raw)
In-Reply-To: <CAKgNAkgxGJad18cAJ53eHAow=nJo6bvpAdLUVGA4+vcjZ11FdA@mail.gmail.com>
On 24/06/2020 09:09, Michael Kerrisk (man-pages) wrote:
> On Tue, 23 Jun 2020 at 17:10, Jonny Grant <jg@jguk.org> wrote:
>>
>> Hello
>> Is it time to remove this old man page? it's two years since it was removed from glibc
>>
>> 2017-08-02: glibc 2.26 released
>>
>> https://man7.org/linux/man-pages/man3/cfree.3.html
>
> The general philosophy is to maintain historical info in man-pages,
> since new manual pages may be installed on an old system. Also, people
> may need to look at old code, and understand what it does.
Fair enough.
Although I would imagine anyone trying to use a function called cfree() would already understand they should use free()
Could the key point that cfree() is deprecated and removed be highlighted at the top of the man page?
I'd be temped to just have :-
DEPRECATED
This function should not be used, it was non-standard and removed in glibc version 2.26 2017-08-02.
NAME
cfree - free allocated memory
Regards
Jonny
next prev parent reply other threads:[~2020-06-24 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 15:10 cfree Jonny Grant
2020-06-23 15:26 ` cfree Ponnuvel Palaniyappan
2020-06-24 8:09 ` cfree Michael Kerrisk (man-pages)
2020-06-24 14:46 ` Jonny Grant [this message]
2020-06-25 7:12 ` cfree Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e87db0e-f7e2-d47f-2a91-e110ffaf343e@jguk.org \
--to=jg@jguk.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).