From: Bruno Haible <bruno@clisp.org>
To: Rich Felker <dalias@libc.org>
Cc: "A. Wilcox" <awilfox@adelielinux.org>,
bug-bison@gnu.org, musl@lists.openwall.com, bug-gnulib@gnu.org
Subject: Re: [musl] Building Bison 3.7 with musl (was Re: portability issues with unicodeio)
Date: Thu, 30 Jul 2020 03:43:40 +0200 [thread overview]
Message-ID: <2117749.CLknGyfR5K@omega> (raw)
In-Reply-To: <20200730000527.GS6949@brightrain.aerifal.cx>
[CCing bug-gnulib]
Rich Felker wrote:
> I don't think the '*' has anything to do with it being a bullet
> character. It's just the implementation-defined replacement character
> musl's iconv uses.
Correct.
> I would guess the code in bison and coreutils printf is assuming the
> non-conforming glibc behavior for iconv of returning an error if a
> character from the input is not exactly representable in the output,
> rather than making replacements and returning the number of inexact
> conversions made.
Yes and no. The code is not making assumptions about a particular iconv()
implementation. But it needs to distinguish two categories of replacements
done by iconv():
- those that are harmless (for example when replacing a Unicode TAG
character U+E00xx with an empty output),
- those that are better not presented to the user, if the programmer has
specified a fallback (for example, replacing all non-ASCII characters
with NUL, '?', or '*').
The standards don't help in making the distinction.
Therefore whether you consider said glibc and libiconv behaviour as
"non-conforming" or not is irrelevant.
I have now adjusted the code to handle musl libc better.
Bruno
next prev parent reply other threads:[~2020-07-30 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 23:23 A. Wilcox
2020-07-29 23:48 ` A. Wilcox
2020-07-30 0:05 ` Rich Felker
2020-07-30 0:12 ` A. Wilcox
2020-07-30 1:43 ` Bruno Haible [this message]
2020-07-30 9:02 ` Florian Weimer
2020-07-30 9:39 ` [musl] Re: iconv replacements Bruno Haible
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=2117749.CLknGyfR5K@omega \
--to=bruno@clisp.org \
--cc=awilfox@adelielinux.org \
--cc=bug-bison@gnu.org \
--cc=bug-gnulib@gnu.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).