From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 06/10] tailq.3: Copy and adapt code from queue.3
Date: Sun, 25 Oct 2020 10:36:48 +0100 [thread overview]
Message-ID: <20201025093651.4616-7-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <20201025093651.4616-1-colomar.6.4.3@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man3/tailq.3 | 26 ++++++++------------------
1 file changed, 8 insertions(+), 18 deletions(-)
diff --git a/man3/tailq.3 b/man3/tailq.3
index 28a7ac509..6f2466cbf 100644
--- a/man3/tailq.3
+++ b/man3/tailq.3
@@ -89,26 +89,14 @@ In the macro definitions,
.Fa TYPE
is the name of a user defined structure,
that must contain a field of type
-.Li SLIST_ENTRY ,
-.Li STAILQ_ENTRY ,
-.Li LIST_ENTRY ,
.Li TAILQ_ENTRY ,
-or
-.Li CIRCLEQ_ENTRY ,
named
.Fa NAME .
The argument
.Fa HEADNAME
is the name of a user defined structure that must be declared
-using the macros
-.Li SLIST_HEAD ,
-.Li STAILQ_HEAD ,
-.Li LIST_HEAD ,
-.Li TAILQ_HEAD ,
-or
-.Li CIRCLEQ_HEAD .
-See the examples below for further explanation of how these
-macros are used.
+using the macro
+.Li TAILQ_HEAD .
.Ss Tail queues
A tail queue is headed by a structure defined by the
.Nm TAILQ_HEAD
@@ -317,10 +305,12 @@ from the tail queue.
.\" .Fa head1
.\" and
.\" .Fa head2 .
-.Pp
-See the EXAMPLES section below for an example program using a tail queue.
.SH RETURN VALUE
.SH CONFORMING TO
+Not in POSIX.1, POSIX.1-2001 or POSIX.1-2008.
+Present on the BSDs.
+(TAILQ functions first appeared in
+.Bx 4.4 ).
.SH BUGS
.SH EXAMPLES
.Ss Tail queue example
@@ -340,9 +330,9 @@ TAILQ_HEAD(tailhead, entry);
int
main(void)
{
- struct entry *n1, *n2, *n3, *np;
+ struct entry *n1, *n2, *n3, *np;
struct tailhead head; /* Tail queue head. */
- int i;
+ int i;
TAILQ_INIT(&head); /* Initialize the queue. */
--
2.28.0
next prev parent reply other threads:[~2020-10-25 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 9:36 [PATCH 00/10] tailq.3: fork " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 01/10] tailq.3: New page that will hold the (tailq) contents of queue.3 Alejandro Colomar
2020-10-25 9:36 ` [PATCH 02/10] queue.3, tailq.3: NAME: Move code from queue.3 to tailq.3 Alejandro Colomar
2020-10-25 9:36 ` [PATCH 03/10] queue.3, tailq.3: SYNOPSIS: " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 04/10] queue.3, tailq.3: DESCRIPTION: " Alejandro Colomar
2020-10-25 9:36 ` [PATCH 05/10] queue.3, tailq.3: EXAMPLES: " Alejandro Colomar
2020-10-25 9:36 ` Alejandro Colomar [this message]
2020-10-25 9:36 ` [PATCH 07/10] tailq.3: ffix: Use man markup Alejandro Colomar
2020-10-25 9:36 ` [PATCH 08/10] tailq.3: Add remaining details to complete the page Alejandro Colomar
2020-10-25 9:36 ` [PATCH 09/10] TAILQ_CONCAT.3, TAILQ_EMPTY.3, TAILQ_ENTRY.3, TAILQ_FIRST.3, TAILQ_FOREACH.3, TAILQ_FOREACH_REVERSE.3, TAILQ_HEAD.3, TAILQ_HEAD_INITIALIZER.3, TAILQ_INIT.3, TAILQ_INSERT_AFTER.3, TAILQ_INSERT_BEFORE.3, TAILQ_INSERT_HEAD.3, TAILQ_INSERT_TAIL.3, TAILQ_LAST.3, TAILQ_NEXT.3, TAILQ_PREV.3, TAILQ_REMOVE.3, TAILQ_SWAP.3: Link to the new tailq(3) page instead of queue(3) Alejandro Colomar
2020-10-25 9:36 ` [PATCH 10/10] queue.3: SEE ALSO: Add tailq(3) Alejandro Colomar
2020-10-25 9:46 ` [PATCH 00/10] tailq.3: fork from queue.3 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=20201025093651.4616-7-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).