public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Bruno Haible <bruno@clisp.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	bug-gnulib@gnu.org,  linux-man@vger.kernel.org
Subject: Re: [PATCH v1 1/1] man/man3/strnul.3: New page
Date: Sun, 22 Feb 2026 15:21:28 +0100	[thread overview]
Message-ID: <aZsQ1ARSAsTm7dnb@devuan> (raw)
In-Reply-To: <aZsPpWJ7yZ1nG2RJ@devuan>

[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]

On 2026-02-22T15:19:35+0100, Alejandro Colomar wrote:
> Hi Bruno,
> 
> On 2026-02-22T15:10:03+0100, Bruno Haible wrote:
> > Alejandro Colomar wrote:
> > > 	 .B #include <string.h>
> > > 	 .P
> > > 	-.BI char\~*strnul(const\~char\~* s );
> > > 	+.BI QChar\~*strnul(QChar\~* s );
> > > 	 .fi
> > 
> > Ouch. This is not understandable. Why should a user learn about what 'QChar'
> > is??
> > 
> > It's basically like a C++ template with 2 instantiations. Just list them
> > explicitly; this will be much clearer.
> > 
> > It's common that the SYNOPSIS section has several lines. For example,
> > man1/locale.1 has 4 separate lines.
> 
> Hmmm; sounds reasonable.  I'll do that.

I've amended the commit to do that:

	commit 0dffb0e8afdd3b025a6001a342b2f49f179a8914 (HEAD -> contrib)
	Author: Alejandro Colomar <alx@kernel.org>
	Date:   2026-02-22 14:34:36 +0100

	    man/man3/strnul.3: SYNOPSIS: Document that it's a const-generic API
	    
	    Document it as two overloads (C++-style).
	    
	    Reported-by: Paul Eggert <eggert@cs.ucla.edu>
	    Suggested-by: Bruno Haible <bruno@clisp.org>
	    Signed-off-by: Alejandro Colomar <alx@kernel.org>

	diff --git a/man/man3/strnul.3 b/man/man3/strnul.3
	index 714b4d191cae..a92ced866a02 100644
	--- a/man/man3/strnul.3
	+++ b/man/man3/strnul.3
	@@ -12,7 +12,8 @@ .SH SYNOPSIS
	 .nf
	 .B #include <string.h>
	 .P
	-.BI char\~*strnul(const\~char\~* s );
	+.BI char\~*strnul(char\~* s );
	+.BI const\~char\~*strnul(const\~char\~* s );
	 .fi
	 .SH DESCRIPTION
	 .BR strnul ()

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-02-22 14:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-21 15:02 [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:02 ` [PATCH v1 1/1] man/man3/strnul.3: New page Alejandro Colomar
2026-02-21 17:41   ` G. Branden Robinson
2026-02-21 19:56     ` Alejandro Colomar
2026-02-21 20:02       ` Simon Josefsson
2026-02-21 20:45         ` Alejandro Colomar
2026-02-21 20:05       ` G. Branden Robinson
2026-02-21 20:55         ` Alejandro Colomar
2026-02-22  1:48   ` Paul Eggert
2026-02-22 11:21     ` Alejandro Colomar
2026-02-22 13:46       ` Alejandro Colomar
2026-02-22 14:10         ` Bruno Haible
2026-02-22 14:19           ` Alejandro Colomar
2026-02-22 14:21             ` Alejandro Colomar [this message]
2026-02-21 15:04 ` [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:09   ` Alejandro Colomar
2026-02-21 20:53 ` [PATCH v2 " Alejandro Colomar
2026-02-21 20:53   ` [PATCH v2 1/1] man/man3/strnul.3: New page Alejandro Colomar

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=aZsQ1ARSAsTm7dnb@devuan \
    --to=alx@kernel.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-man@vger.kernel.org \
    /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