From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: Gabriel Ravier <gabravier@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH v2 1/1] vfprintf: support C2x %b and %B conversion specifiers
Date: Sat, 15 Apr 2023 16:15:50 +0200 [thread overview]
Message-ID: <20230415161550.1fb92f4e@inria.fr> (raw)
In-Reply-To: <cc5e0c93-9aee-f287-fcfa-37829437dd9b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
Gabriel,
on Sat, 15 Apr 2023 15:15:48 +0200 you (Gabriel Ravier
<gabravier@gmail.com>) wrote:
> > What is still missing then, is to add PRIxYYY macros. With the
> > latest draft
> >
> > https://open-std.org/JTC1/SC22/WG14/www/docs/n3096.pdf
> >
> > these become mandatory feature tests for this feature. I already
> > have a patch for that.
> Nice to have a patch for that too, thanks. I wasn't planning on
> adding them myself, mostly because I don't really have any tests for
> them (as opposed to the b/B conversion specifiers which I have plenty
> of tests for) and don't plan on adding any anytime soon.
As said they are now mandatory, because the `B` also changes state
from just "recommended" to "recommended optional". The git message
could also reflect that.
What I noticed after sending my mail, you are also missing to do the
same for vfwprintf which unfortunately doubles the logic, here. A
refactoring for these two functions could probably gain some kilo or
so.
> > And I will soon be starting on the similar features for `scanf` and
> > friends. There is one problem zone for that, namely that `0b`
> > prefixes are not only extensions but change semantics of existing
> > executables that would be linked against different versions of the
> > C library.
> >
> > My plan is to make the distinction deep down in `__intscan` and have
> > that internal function in two versions `__intscan_c17` and
> > `__intscan_c23`, say.
> Doesn't the same apply to strto{,u}l{,l} given the behavior change is
> caused by the corresponding change in those functions ?
Yes. I have a very generous notion of "friend" ;-)
They all use that same function __intscan underneath, so this factors
out cleanly, it seems.
Thanks
Jₑₙₛ
--
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Université de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA Nancy Grand Est :::::::::::::::::::::::: Camus ::
:: :::::::::::::::::::::::::::::::::::: ☎ +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-04-15 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 16:36 [musl] [PATCH] " Gabriel Ravier
2022-09-12 13:59 ` Rich Felker
2022-09-12 14:42 ` Jₑₙₛ Gustedt
2022-09-19 15:09 ` Rich Felker
2022-09-19 17:59 ` Szabolcs Nagy
2022-09-19 18:10 ` Rich Felker
2022-09-20 9:19 ` Jₑₙₛ Gustedt
2022-09-20 12:28 ` Rich Felker
2022-09-20 13:29 ` Jₑₙₛ Gustedt
2022-09-20 13:55 ` Rich Felker
2022-09-20 14:08 ` Jₑₙₛ Gustedt
2022-09-20 14:15 ` Rich Felker
2022-09-20 14:22 ` Jₑₙₛ Gustedt
2022-09-20 14:27 ` Jₑₙₛ Gustedt
2022-09-20 14:46 ` Rich Felker
2022-09-20 15:20 ` Jₑₙₛ Gustedt
2023-04-15 12:28 ` [musl] [PATCH v2 0/1] " Gabriel Ravier
2023-04-15 12:28 ` [musl] [PATCH v2 1/1] " Gabriel Ravier
2023-04-15 12:52 ` Jₑₙₛ Gustedt
2023-04-15 13:15 ` Gabriel Ravier
2023-04-15 14:15 ` Jₑₙₛ Gustedt [this message]
2023-04-16 6:51 ` Jₑₙₛ Gustedt
2023-04-16 13:20 ` Gabriel Ravier
2023-04-16 14:39 ` Rich Felker
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=20230415161550.1fb92f4e@inria.fr \
--to=jens.gustedt@inria.fr \
--cc=gabravier@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).