Skip Menu |

This queue is for tickets about the Digest-Whirlpool CPAN distribution.

Report information
The Basics
Id: 4526
Status: resolved
Priority: 0/
Queue: Digest-Whirlpool

People
Owner: Nobody in particular
Requestors: gisle [...] aas.no
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.0.2
Fixed in: (no value)



Subject: base64digest should be b64digest
The interface speced out in Digest.pm say that the base64 method should be named 'b64digest'. You use 'base64digest'. I think what you should do is inherit from 'Digest::base' so that you get the "official" behaviour. You might then also make your 'base64digest' just call b64digest.
[guest - Sat Nov 29 07:19:49 2003]: Show quoted text
> The interface speced out in Digest.pm say that the base64 method > should be named 'b64digest'. You use 'base64digest'. > > I think what you should do is inherit from 'Digest::base' so that > you get the "official" behaviour. You might then also make your > 'base64digest' just call b64digest.
OK, I'll remove my base64digest() method in the next release of Whirlpool to prevent redundancy. Same goes for Haval256.
On Sat Nov 29 07:19:49 2003, guest wrote: Show quoted text
> The interface speced out in Digest.pm say that the base64 method > should be named 'b64digest'. You use 'base64digest'. > > I think what you should do is inherit from 'Digest::base' so that > you get the "official" behaviour. You might then also make your > 'base64digest' just call b64digest.
This has been resolved in version 1.0.4. base64digest is still there via a symbol table alias however for backwards compatability