From: Alejandro Colomar <alx@kernel.org>
To: Vincent Lefevre <vincent@vinc17.net>,
libc-alpha@sourceware.org, Eric Blake <eblake@redhat.com>,
linux-man@vger.kernel.org
Subject: Re: LINE_MAX
Date: Tue, 21 May 2024 12:08:13 +0200 [thread overview]
Message-ID: <6wyb3mkthtzlyknwasft2fwolujrpeldsw272eqppdsv5qwxcq@mzvxfyd6epoh> (raw)
In-Reply-To: <20240520222658.GG2665@qaa.vinc17.org>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Hi Vincent,
On Tue, May 21, 2024 at 12:26:58AM GMT, Vincent Lefevre wrote:
> On 2024-05-20 23:49:13 +0200, Alejandro Colomar wrote:
> > I think I found a bug in POSIX.1-2017 (and probably, previous ones too,
> > but didn't check).
>
> I already reported the issue in 2009 about the example:
Thanks!
> See thread "fgets/strtok and LINE_MAX" I started on 2009-09-21
> in the Austin Group mailing-list. It is available on gmane:
>
> Path: news.gmane.org!not-for-mail
> From: Vincent Lefevre <vincent-opgr-opTGSl+ZDNkdnm+yROfE0A@public.gmane.org>
> Newsgroups: gmane.comp.standards.posix.austin.general
> Subject: fgets/strtok and LINE_MAX
> Date: Mon, 21 Sep 2009 01:03:13 +0200
> Lines: 31
> Approved: news@gmane.org
> Message-ID: <20090920230313.GV657@prunille.vinc17.org>
> [...]
Hmmm, how does that thing work? Any http link available?
>
> There's the issue with the missing "+1", but also whether
> LINE_MAX < INT_MAX.
I guess the LINE_MAX <? INT_MAX issue is not an actual issue as long as
implementations do the Right Thing and don't set it to >= INT_MAX.
> See also
> https://www.austingroupbugs.net/view.php?id=182
Thanks!
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-21 10:08 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 ` Alejandro Colomar [this message]
2024-05-21 11:40 ` LINE_MAX Vincent Lefevre
2024-05-20 22:35 ` LINE_MAX Lennart Jablonka
2024-05-21 10:14 ` LINE_MAX 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=6wyb3mkthtzlyknwasft2fwolujrpeldsw272eqppdsv5qwxcq@mzvxfyd6epoh \
--to=alx@kernel.org \
--cc=eblake@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=vincent@vinc17.net \
/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).