I think you need a debugging perl for the environment var to work. [...] you can get the same effect from Hash::Util::hash_seed()
Both environment variables shown in the OP seem to be working:
$ PERL_HASH_SEED_DEBUG=1 perl -MHash::Util=hash_seed -le'print hash_se
+ed'
HASH_SEED = 165032588
165032588
$ PERL_HASH_SEED_DEBUG=1 perl -MHash::Util=hash_seed -le'print hash_se
+ed'
HASH_SEED = 725441538
725441538
tye's getKeyCollisions shows always the same output here:
$ PERL_HASH_SEED_DEBUG=1 perl gkc.pl | md5sum
HASH_SEED = 501557310
e4d6401f730eede592733482fac0ec61 -
$ PERL_HASH_SEED_DEBUG=1 perl gkc.pl | md5sum
HASH_SEED = 1324598606
e4d6401f730eede592733482fac0ec61 -
I don't know if it's supposed to do so or not. I'm beginning to take a fancy to this :) since it seems to be impossible to obtain some different output of anything between runs of perl (well, anything except hash seeds!).
-
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.
|