in reply to Re^2: Understanding pack and unpack changes for binary data between 5.8 and 5.10
in thread Understanding pack and unpack changes for binary data between 5.8 and 5.10

I don't see the problem.

use strict; use warnings; use Data::Dumper qw( Dumper ); $Data::Dumper::Useqq = 1; $Data::Dumper::Terse = 1; $Data::Dumper::Indent = 0; my $s = chr(0xC9); utf8::downgrade($s); print(Dumper(unpack('H*', $s)), "\n"); utf8::upgrade($s); print(Dumper(unpack('H*', $s)), "\n"); print(Dumper(unpack('H*', "\x{C9}\x{2660}")), "\n");

5.10.0:

"c9" # Ok "c9" # Ok Character in 'H' format wrapped in unpack at 750077.pl line 16. "c960" # GIGO

The internal representation is and should be irrelevant.

If you want to see the internal representation, it stands to reason that you should have to explicitely fetch it.

Replies are listed 'Best First'.
Re^4: Understanding pack and unpack changes for binary data between 5.8 and 5.10
by almut (Canon) on Mar 12, 2009 at 09:24 UTC
    I don't see the problem...

    I don't see a problem either.  I just pointed out a difference, i.e. that something which people might have gotten used to, no longer behaves the way it did before...