All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, Yedidyah Bar David <didi@redhat.com>
Subject: [PATCH v1b] isalpha.3: Move NOTES to CAVEATS, and clarify some Undefined Behavior
Date: Mon,  5 Jun 2023 13:38:37 +0200	[thread overview]
Message-ID: <20230605113836.8496-1-alx@kernel.org> (raw)
In-Reply-To: <14cbb4e3-9302-8065-2320-978181fbede0@gmail.com>

Reported-by: Yedidyah Bar David <didi@redhat.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---

I suggest this instead.

 man3/isalpha.3 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/man3/isalpha.3 b/man3/isalpha.3
index 000e816d7..721ca8972 100644
--- a/man3/isalpha.3
+++ b/man3/isalpha.3
@@ -345,13 +345,15 @@ .SH HISTORY
 .TP
 .BR isascii_l ()
 glibc 2.3.
-.SH NOTES
+.SH CAVEATS
 The standards require that the argument
 .I c
 for these functions is either
 .B EOF
 or a value that is representable in the type
-.IR "unsigned char" .
+.IR "unsigned char" ;
+otherwise,
+the behavior is undefined.
 If the argument
 .I c
 is of type
-- 
2.40.1


  reply	other threads:[~2023-06-05 11:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 11:17 [PATCH] isalpha.3: behavior is undefined if c is out-of-range Yedidyah Bar David
2023-06-05 11:33 ` Alejandro Colomar
2023-06-05 11:38   ` Alejandro Colomar [this message]
2023-06-05 11:41     ` [PATCH v1b] isalpha.3: Move NOTES to CAVEATS, and clarify some Undefined Behavior Sam James
2023-06-05 12:43     ` Yedidyah Bar David
2023-06-05 12:09   ` [PATCH v2alx] " Alejandro Colomar
2023-06-05 12:34   ` [PATCH] isalpha.3: behavior is undefined if c is out-of-range Yedidyah Bar David
2023-06-05 13:15     ` Alejandro Colomar
2023-06-05 13:17       ` Alejandro Colomar
2023-06-05 13:29       ` Yedidyah Bar David
2023-06-13 14:07         ` Yedidyah Bar David
2023-07-08 18:42           ` 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=20230605113836.8496-1-alx@kernel.org \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=didi@redhat.com \
    --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 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.