public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Zack Weinberg <zackw@panix.com>,
	"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: queue.7, stailq.3, (simpleq.3): Document SIMPLEQ as an alias of STAILQ
Date: Wed, 10 Feb 2021 22:16:35 +0100	[thread overview]
Message-ID: <7e5e14ee-9fce-27a0-07b9-803f4fafa287@gmail.com> (raw)
In-Reply-To: <CAKCAbMgpXzH3nFyyn3fO3rjwNsG1ZBEkK89ce6r1JLPQL9oKZA@mail.gmail.com>

Hello Zack,,On 2/10/21 4:38 PM, Zack Weinberg wrote:
> On Wed, Feb 10, 2021 at 10:13 AM Alejandro Colomar (man-pages) via
> Libc-alpha <libc-alpha@sourceware.org> wrote:
>>> BTW, a suggestion for glibc:  glibc could simplify the code with things like
>>>
>>> #define SIMPLEQ_ENTRY(type) STAILQ(type)
>> s/STAILQ/&_ENTRY/
>>>
>>> It would make it more obvious that they're the same thing.
> 
> I don't know about anyone else on the glibc team, but I personally
> consider the entirety of <sys/queue.h> to be provided only for some
> degree of backward compatibility with old applications that were
> ported from BSD; new code should not use it.  I'd *like* to formally
> deprecate it, but I expect that would cause too much breakage to be
> viable.  Anyway, I hope you can understand why I'm not interested in
> messing with its contents at all.
> 
> (Can we add a statement to the effect that new code should not use
> <sys/queue.h> to all of the related manpages, please?)

I'm not against this, as I think I commented in the past.
But I'd prefer to have some rough consensus about this from
the glibc team before making suchg a change.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  parent reply	other threads:[~2021-02-10 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 15:06 queue.7, stailq.3, (simpleq.3): Document SIMPLEQ Alejandro Colomar (man-pages)
2021-02-10 15:11 ` queue.7, stailq.3, (simpleq.3): Document SIMPLEQ as an alias of STAILQ Alejandro Colomar (man-pages)
2021-02-10 15:13   ` Alejandro Colomar (man-pages)
2021-02-10 15:38     ` Zack Weinberg
2021-02-10 15:53       ` Alejandro Colomar (man-pages)
2021-02-10 16:05         ` Zack Weinberg
2021-02-10 16:24           ` Alejandro Colomar (man-pages)
2021-02-10 16:36             ` Zack Weinberg
2021-02-10 21:16       ` Michael Kerrisk (man-pages) [this message]
2021-02-10 21:30 ` queue.7, stailq.3, (simpleq.3): Document SIMPLEQ 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=7e5e14ee-9fce-27a0-07b9-803f4fafa287@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=zackw@panix.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