Status: Accepted Owner: nicolas....@gmail.com Labels: Type-Enhancement Priority-Low
New issue 96 by nicolas....@gmail.com: Using >> (bitShift:) instead of pow (raisedTo:) http://code.google.com/p/cog/issues/detail?id=96
By virtue of SLANG translation, interpreterAllocationReserveBytes uses pow((double)2,(double)n) to answer an int, wouldn't it better to just use a bit shift?
2^n <=> 1<<n, up to n=31 I doubt we reserve more than that, the result is signed anyway.
And this would remove yet another warning.
Attachments: interpreterAllocationReserveBytes.st 2.0 KB
Comment #1 on issue 96 by guillermopolito@gmail.com: Using >> (bitShift:) instead of pow (raisedTo:) http://code.google.com/p/cog/issues/detail?id=96
Mirrored in https://pharo.fogbugz.com/default.asp?pre=preMultiSearch&pg=pgList&p...
vm-dev@lists.squeakfoundation.org