public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: libc-alpha@sourceware.org, Eric Blake <eblake@redhat.com>,
	 linux-man@vger.kernel.org
Subject: Re: LINE_MAX
Date: Tue, 21 May 2024 12:14:02 +0200	[thread overview]
Message-ID: <6u577ud6lqgsef7titpg6ngfuhxw7yvuzkhlrzo6shrrq3jlgl@rblynlq4fm53> (raw)
In-Reply-To: <ZkvQIlVNJ-aYs9RI@fluorine>

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

Hi Lennart,

On Mon, May 20, 2024 at 10:35:14PM GMT, Lennart Jablonka wrote:
> Quoth Alejandro Colomar:
> > I think I found a bug in POSIX.1-2017 (and probably, previous ones too,
> > but didn't check).

[...]

> > This example seems to contradict my understanding of what limits.h says.
> > 
> > So, either limits.h should be explicit that the trailing null byte is
> > also included in LINE_MAX, or the example is bogus and should be fixed.
> > I guess it's the latter, although I wish it was the former, so we can
> > avoid a +1 in the code.
> > 
> > In any case, could you please forward this to the Austin group?
> 
> Good find.  You aren’t the first one to find it:

:-)

> https://austingroupbugs.net/view.php?id=182 discusses that example a little.
> The desired action written there appears verbatim (bar formatting) in the
> 4.1 draft of POSIX.1-202x.

Could you please paste that part of the draft?  It's quite inaccessible
to me.  And since the info is already public in the ticket, I guess it's
not a violation of anything.

Have a lovely day!
Alex

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

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

      reply	other threads:[~2024-05-21 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 21:49 LINE_MAX Alejandro Colomar
2024-05-20 22:26 ` LINE_MAX Vincent Lefevre
2024-05-21 10:08   ` LINE_MAX Alejandro Colomar
2024-05-21 11:40     ` LINE_MAX Vincent Lefevre
2024-05-20 22:35 ` LINE_MAX Lennart Jablonka
2024-05-21 10:14   ` Alejandro Colomar [this message]

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=6u577ud6lqgsef7titpg6ngfuhxw7yvuzkhlrzo6shrrq3jlgl@rblynlq4fm53 \
    --to=alx@kernel.org \
    --cc=eblake@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).