As oshalla pointed out, pack 'b*' pads the string to the nearest byte.

In order to know how much you need to trim off after you've unpack'd it, you need to also remember how many binary bits need trimming off the unpacked binary; 0, 2, 4, 6.

You can do that by prefixing the packed data with an extra byte that contains that information:

Update: My math was completely wrong and only worked for the example through blind luck. I've cleaned that up and wrapped the conversions in subroutines:

my %charmap = ( A => '00', C => '01', G => '10', T => '11', ); sub packACGT { ( my $in = shift ) =~ s/(.)/$charmap{$1}/ge; print length $in, ':', length( $in ) % 8; pack 'Cb*', ( 0, 6, 4, 2 )[ length( $in ) % 8 / 2 ], $in; } my %digmap = ( '00' => "A", '01' => "C", '10' => "G", '11' => "T", ); sub unpackACGT { my( $len, $out ) = unpack 'Cb*', shift; print $len; substr( $out, -$len ) = '' if $len; $out =~ s/(..)/$digmap{$1}/ge; return $out; } my $string = $ARGV[0] || 'GATTACCCC'; print length( $string ), ':', $string; my $compressed = packACGT( $string ); print length( $compressed ), ':', "'$compressed'"; my $decompressed = unpackACGT( $compressed ); print length( $decompressed ), ':', $decompressed;

It would be a nice enhancement to pack and unpack to allow the n/A* syntax to deal with this.

So that pack 'c/b*', ... and unpack 'c/b*', ... would work.


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.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Unpack Fail to Decompress String? by BrowserUk
in thread Unpack Fail to Decompress String? by neversaint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.