Front page | perl.perl5.porters |
Postings from May 2013
On 05/01/2013 05:22 PM, Dave Mitchell wrote:
> I think the issue can be summed up as:
[snip]
> * Some of those fixes have clashes withg your mental model of how pack
> should work.
I disagree...
a A string with arbitrary binary data, will be null padded.
A A text (ASCII) string, will be space padded.
... because I fail to see how $out = pack("v/a", $stuff) (same for v/A)
should ever have $out have the UTF8 flag set given the above.
I appreciate that you already said you consider the particular behaviour
a bug, but I read that as "the fact that the UTF8ness of the output
breaks your length integer is a bug" not "that should never result in a
scalar with the utf8 flag set". The following paragraph assumes that
understanding of what you said:
IOW, is there any reason why pack() would ever result in a scalar with
the UTF8 bit set? I don't think so. pack() will create a series of bytes
(well, octets), not characters because an arbitrary combination of pack
templates will always produce something that mixes in output that isn't
based on characters.
--Steffen
Thread Previous
|
Thread Next