mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Is c16rtomb a buggy/underspecified API, or is it just me?
Date: Sun, 7 Sep 2014 12:24:43 -0400	[thread overview]
Message-ID: <20140907162443.GA20128@brightrain.aerifal.cx> (raw)

I was looking at how much work would be involved in adding uchar.h
functions (one of the few remaining C11 items), and I can't seem to
figure out how c16rtomb is supposed to work. It's presumably for
converting UTF-16 to the locale's multibyte encoding (UTF-8 in our
case), since the opposite-direction function (mbrtoc16) has provisions
for generating pairs of surrogates, but I can't see any provisions in
the specification of c16rtomb for what it does when it gets the first
of a pair of surrogates and thus isn't ready to produce any output.

http://port70.net/~nsz/c/c11/n1570.html#7.28.1.2

Any ideas?

Rich


                 reply	other threads:[~2014-09-07 16:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140907162443.GA20128@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).