So it is clear that Digest::JHash has a problem in that it doesnt faithfully reproduce lookup2.c like it thinks it does.
I think i should report my findings to them.
But should they "fix" it?
If they do, the new version while now returning the results lookup2.c does will no longer always return the same results 0.10 did.
This would be a huge problem to users of the module, some of their hashs have now changed.
In thinking about it, i dont think the negative rather than positive additions of the chars makes it "less hashy", just differnt from lookup2.c.
What would you do if faced with this dilemma?
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.