From: Bruno Haible <bruno@clisp.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] swprintf cannot handle the character 0xff
Date: Tue, 13 Jun 2023 02:23:37 +0200 [thread overview]
Message-ID: <7531906.nlapOpYt14@nimes> (raw)
In-Reply-To: <20230612235437.GF4163@brightrain.aerifal.cx>
Rich Felker wrote:
> I wonder if this should actually be a defect and if wide printf should
> be specified as converting the value, converted to (unsigned char), as
> if by btowc, rather than the raw value.
I agree. If ISO C and POSIX had specified or would specify %c in wide printf
like this, it would eliminate a (small) pitfall for programmers.
Bruno
prev parent reply other threads:[~2023-06-13 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 12:30 Bruno Haible
2023-06-12 20:22 ` Rich Felker
2023-06-12 21:01 ` Rich Felker
2023-06-12 21:13 ` Rich Felker
2023-06-12 23:09 ` Bruno Haible
2023-06-12 23:54 ` Rich Felker
2023-06-13 0:23 ` Bruno Haible [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=7531906.nlapOpYt14@nimes \
--to=bruno@clisp.org \
--cc=dalias@libc.org \
--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).