From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Funktion for converting strings from / to UTF-16 and UTF-32?
Date: Mon, 29 Apr 2019 18:24:12 -0400 [thread overview]
Message-ID: <20190429222412.GW23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <8959bfe3-14ac-1fa5-7423-d3e093d81e11@informatik.uni-freiburg.de>
On Mon, Apr 29, 2019 at 08:27:35PM +0200, Philipp Klaus Krause wrote:
> Would musl be interested in adding support for functions that convert
> from / to UTF-16 and UTF-32 (assuming that char16_t is UTF-16 and
> char32_t is UTF-32)?
>
> There is the proposal N 2282, which was discussed half a year ago at the
> Pittsburg meeting of WG 14; back then the comitee wanted to see a second
> implementation fo these functions (the library that comes with SDCC
> already has them).
I'm not sure. They seem to be of limited usefulness - UTF-16 is
legacy, and UTF-32 is the same as wchar_t on any implementation that
actually supports UTF-32 (at least wchar_t has to cover the whole
Unicode codepoint space, so 16-bit is out and the only reason it could
be anything other than UTF-32 is gratuitous incompatibility).
Of course we'll support this if it's standardized as a required
interface for future C versions, but I'm not sure it's in line with
musl's philosophy or criteria for inclusion to be trying to advance
these interfaces into a standard without a good argument that they're
important to have (if you believe they are, I'm open to hearing that
and seeing what others think).
Rich
next prev parent reply other threads:[~2019-04-29 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 18:27 Philipp Klaus Krause
2019-04-29 22:24 ` Rich Felker [this message]
2019-04-30 21:14 Philipp Klaus Krause
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=20190429222412.GW23599@brightrain.aerifal.cx \
--to=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).