As intended, yes. But not as expected from what digit usually means (any of the arabic figures of 1 through 9 and 0. [3]).
digitAt: answers a byte in an integer and so is working as intended.
Eliot (phone)Hi, try to run the following:(2 raisedTo: 100000) digitAt: 1
The expected result (if I understood what digitAt: should return) is 9, but the message returns 0 instead. In fact, it returns 0 for any index.Is this a bug or am I missunderstanding how digitAt: should work?Cheers,Bernat Romagosa.p.s. My config is Pharo 1.2 with a 'Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.51]' on Debian Lenny.