All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Issue in man page regex.3
Date: Sun, 22 Jan 2023 21:32:30 +0100	[thread overview]
Message-ID: <dc5054e5-e648-5879-cb3f-feaeefa20545@gmail.com> (raw)
In-Reply-To: <20230122193127.GA28944@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

Hi Helge,

On 1/22/23 20:31, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    null-terminated → NUL-terminated

I prefer NUL-terminated too, but there's a historic tradition of using 
null-terminated and similar syntax in the manual pages.  The intent is to reduce 
confusion between NUL and NULL.  See man-pages(7).

I believe that doesn't make any sense, since there's at least some visual 
difference between NUL and NULL, but the isn't any difference between null and 
null (apart from the context).

Sooo, I may apply policy change to stop using English syntax for these terms, 
and start using NUL and NULL consistently.

Cheers,

Alex


> 
> "B<regexec>()  is used to match a null-terminated string against the"
> "precompiled pattern buffer, I<preg>.  I<nmatch> and I<pmatch> are used to"
> "provide information regarding the location of any matches.  I<eflags> is the"
> "bitwise-B<or> of zero or more of the following flags:"

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

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

  reply	other threads:[~2023-01-22 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 19:31 Issue in man page regex.3 Helge Kreutzmann
2023-01-22 20:32 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 21:03 ` Alejandro Colomar
2023-01-23 17:47   ` Helge Kreutzmann
2023-01-23 19:03     ` G. Branden Robinson
2023-01-23 20:14       ` Helge Kreutzmann
2023-03-11 17:13 Helge Kreutzmann
2025-08-24 14:48 Helge Kreutzmann

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=dc5054e5-e648-5879-cb3f-feaeefa20545@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.