Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH]

On 7 June 2012 17:33, Aristotle Pagaltzis <pagaltzis@gmx.de> wrote:
> * Jim Avera <perlbug-followup@perl.org> [2012-05-26 03:10]:
>> However it seems wrong to test for #chars != #bytes, because binary
>> data _should_ be passed as byte strings, that is, with Perl's internal
>> utf8 flag off.
>
> Disagree.
>
> The UTF8 flag is completely irrelevant to a string’s semantics.

Please stop saying this. It is the same flawed logic that means I cant
send a bitvector in JSON reliably, which is a problem we DO NOT WANT
in Perl.

It is simply not true. If a string contains binary data then it is
binary, and treating it as utf8 in any form is completely and utterly
wrong.

cheers
Yves
-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

• [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by Jim Avera
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by demerphq
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by Aristotle Pagaltzis
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by demerphq
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by demerphq
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by Jesse Luehrs
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by demerphq
• Re: [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by Jesse Luehrs
• [perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH] by Father Chrysostomos via RT
• proposed/drafted new perl docs by Uri Guttman
• Re: proposed/drafted new perl docs by Ricardo Signes
• Re: proposed/drafted new perl docs by Nicholas Clark