From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: Ping Re: [v3] C2x strtol binary constant handling
Date: Fri, 30 Dec 2022 15:24:02 +0000 [thread overview]
Message-ID: <6a2ee43-535-2765-749a-60aa17ceb4cc@codesourcery.com> (raw)
In-Reply-To: <8feb794b-7d20-2ba0-1a7a-62f8c9919cba@codesourcery.com>
Ping. This patch
<https://sourceware.org/pipermail/libc-alpha/2022-December/144235.html>,
and the scanf followup
<https://sourceware.org/pipermail/libc-alpha/2022-December/144250.html>,
are pending review.
I'll note for completeness that AFNOR comment FR-228 on the C2x CD
expresses concern about the semantic change (see section 16 in N3072).
Given that accepting 0b and 0B for base 2 strtol was an explicit change in
a paper accepted by WG14 with no votes against (and I think I mentioned
the consequences for strtol base 0 and scanf %i when binary constants were
added), I don't think that comment is particularly likely to result in any
changes to the working draft (and likewise for the point in the AFNOR
comment about strtol not accepting digit separators - that was also an
explicit change in the paper adding digit separators), but if it does
result in any changes at the ballot resolution meeting (23-27 January)
there would still be time to revert these changes before glibc 2.37 is
released.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-12-30 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:37 Joseph Myers
2022-12-15 12:25 ` Alejandro Colomar
2022-12-15 19:09 ` Adhemerval Zanella Netto
2022-12-19 16:02 ` [v2] " Joseph Myers
2022-12-22 0:10 ` [v3] " Joseph Myers
2022-12-30 15:24 ` Joseph Myers [this message]
2023-01-16 13:52 ` Adhemerval Zanella Netto
2023-01-16 19:23 ` Joseph Myers
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=6a2ee43-535-2765-749a-60aa17ceb4cc@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).