But if they are to be added to the Crypto module, they should be fixed to follow the same API as the other hash functions though. I think that'd be preferable regardless where in Pike they're added, as well. Besides, the naming convention for functions in Pike is_like_this, and notthisway.
If there is a consensus about adding the module to Crypto I'd happily adapt the module to be more like other hash functions, and follow naming conventions better.
I'd rather have it in crypto than not having it at all, and the consensus building on the proper place to put it seems to have died out.
Peter Bortas @ Pike developers forum wrote:
consensus building on the proper place to put it seems to have died out.
Meaning: there were no counterarguments anymore to the latest pro-Crypto arguments, and therefore there is consensus to put it there.
pike-devel@lists.lysator.liu.se