Other workarounds for the vec > 2**31 offsets bug?
My crude approach to extending the addressable bit range to 2**32-1 would be to divide the offset by 2 and operate in units of 2 bits. Something like this:
sub setbit {
# args: var, offset, value (0/1)
if ($_[1] % 2) { # odd offset
if ($_[2]) {
vec($_[0], $_[1]/2, 2) |= 0b10; # set
} else {
vec($_[0], $_[1]/2, 2) &= 1; # clear
}
} else { # even offset
if ($_[2]) {
vec($_[0], $_[1]/2, 2) |= 1; # set
} else {
vec($_[0], $_[1]/2, 2) &= 0b10; # clear
}
}
}
my $v = "";
setbit($v, 2**32-1, 1); # set bit
setbit($v, 2**32-1, 0); # clear bit
(and likewise for reading a bit)
The idea could in principle be extended to other unit sizes (4, 8, ...), though the bit fiddling would then be somewhat more involved.
-
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.