there are reasons other than performance for wanting fix-width integer semanticsDefinitely correct ... though I must confess that the reasons you've implicitly put forward in your demos were not exactly what I was thinking of when I acknowledged this (or tried to) in my earlier post. For a Math::GMPz rendition of your demo I would put forward the following:
#! perl -slw
use strict;
use Math::GMPz qw(:mpz);
my $ZERO = Math::GMPz->new( 0 );
my $ONE = Math::GMPz->new( 1 );
#my $ALLONES = ~ $ZERO;
my $ALLONES = (Math::GMPz->new(1) << 128) - 1;
my $MASK1 = $ALLONES / 3;
my $MASK2 = $ALLONES / 15 * 3;
my $MASK3 = $ALLONES / 255;
my $MASK4 = $MASK3 * 15;
my $bits = Math::GMPz->new( 0 );
## set every 3rd bit
$bits |= $ONE << $_ for map $_*3+1, 0 .. 42;
print $bits;
## count the bits (43)
#print bcount( $bits );
print Rmpz_popcount($bits);
## now invert them and count again. (85)
#print bcount( ~$bits );
print Rmpz_popcount($ALLONES ^ $bits);
I hope it doesn't miss the point ... I think the only changes are that:
1) It changes the way that $ALLONES is created;
2) It removes the need for sub bcount() Update: And, there's also now a qw(:mpz) in the third line. Cheers, Rob
-
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.
|