I had the same problem. I added the following to my compatibility package. In Pharo now I do: shaHashMessage: aString "this method hashes aString using a SHA1 (SecureHashAlgorithm) method. Returns an integer" ^ (SHA1 new hashStream: aString readStream) asInteger (which works in 2.0 and 3.0) and in gemstone I do: shaHashMessage: aString "this method hashes aString using a SHA1 (SecureHashAlgorithm) method. Returns an integer" ^ SecureHashAlgorithm new hashMessage: aString On Wed, May 7, 2014 at 12:17 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 07 May 2014, at 16:43, phil@highoctane.be wrote:
hashStage1 is a LargePositiveInteger...
Quite different thing.
No, not really
123 asByteArrayOfSize: 4
#[0 0 0 123]
#[0 0 0 123] asInteger
123
-- Mariano http://marianopeck.wordpress.com