This can be generalised for other orderings of the bytes, and of the bits in each byte, of the bitstring. Four types of bitstring can be identified:
big-endian: ms-bit of first byte is the ms-bit of the multi-byte number. This is handled as shown, ie: my $h = unpack( 'H*', $bitstring ) ;
little-endian: ls-bit of first byte is the ls-bit of the multi-byte number. This is handled: my $h = unpack( 'H*', scalar reverse $bitstring ) ;
Note that this is the same order as vec($v, $b, 1)
big-endian reversed bytes: ls-bit of first byte is the ms-bit of the multi-byte number. This is handled: my $h = unpack( 'H*', pack('b*', unpack('B*', $bitstring)) ) ;
little-endian reversed bytes: ms-bit of first byte is the ls-bit of the multi-byte number. This is handled: my $h = unpack( 'H*', pack('b*', unpack('B*', scalar reverse $bitstr
+ing)) ) ;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|