pp \$a;;
[Malformed UTF-8 character (fatal) at C:/Perl64/lib/Data/Dump.pm line
+458, <STDIN> line 13.
print unpack 'H*', $a;;
Malformed UTF-8 character (byte 0xfe) in unpack at (eval 21) line 1, <
+STDIN> line 14.
Malformed UTF-8 character (unexpected continuation byte 0x84, with no
+preceding start byte) in unpack
Malformed UTF-8 character (unexpected continuation byte 0x80, with no
+preceding start byte) in unpack
Malformed UTF-8 character (unexpected continuation byte 0x80, with no
+preceding start byte) in unpack
Malformed UTF-8 character (unexpected continuation byte 0x80, with no
+preceding start byte) in unpack
Malformed UTF-8 character (unexpected continuation byte 0x80, with no
+preceding start byte) in unpack
Malformed UTF-8 character (unexpected continuation byte 0x80, with no
+preceding start byte) in unpack
4100000000000000
And perl already has a perfectly good mechanism for packing integers into strings.
It also means that you now have a mechanism that will allow you to construct a string of packed integers that Perl has no way of unambiguously deconstructing.
I look forward to seeing that deperecated & removed sometime soon.
And it has no bearing upon the original desicussion because SvPVbytes() wouldn't know what to do with it either.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
|