develooper Front page | perl.perl5.porters | Postings from December 2010

Re: RFC: Summary of proposed handling of surrogates, non-characters,etc for 5.14. Note some backward incompatibility

Thread Previous | Thread Next
From:
Eric Brine
Date:
December 20, 2010 09:26
Subject:
Re: RFC: Summary of proposed handling of surrogates, non-characters,etc for 5.14. Note some backward incompatibility
Message ID:
AANLkTinCj72WrQRB0n+nmbN_CS3cQ2V+3JJhph9KJwKJ@mail.gmail.com
On Mon, Dec 20, 2010 at 4:27 AM, demerphq <demerphq@gmail.com> wrote:

> > I *am* very opposed to surrogate codepoints behaving differently from
> > non-surrogate codepoints under the allow-any-UV-codepoint paradigm.
>
> Why shouldn't perl warn when it tries to lc() a string containing a
> surrogate pair instead of the correctly decoded true codepoint the
> surrogate pair represents?
>

So you suggest we warn for code points that *can not* be encoded in UTF-16,
but remain silent for code points that *must not* be encoded in UTF-16 (e.g.
0xFFFE)? If anything, that sounds backwards. Why warn for what already fails
safe.

I don't see any reason to some non-characters differently than other
non-characters either.

- Eric


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About