develooper Front page | perl.perl5.porters | Postings from May 2013

Re: How on earth did we manage to break pack() so badly?

Thread Previous | Thread Next
Peter Martini
May 1, 2013 16:10
Re: How on earth did we manage to break pack() so badly?
Message ID:
On Wed, May 1, 2013 at 11:22 AM, Dave Mitchell <> wrote:
> But that's just leaking the internal implementation details.

I thought that was the point of pack/unpack?  From the top of the docs
for pack: "Typically, each converted value looks like its
machine-level representation"

I understand the point being made that the internal format of the
string buffer is an implementation detail, but I'd think a better
default would be to pack that string buffer as asked rather than
convert it to something that is guaranteed to not be a machine-level

It seems a warning when trying to pack/unpack a string with the UTF
bit set (pointing to encode, etc) would make more sense than
converting the machine level representation to an idealized


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About