4 ms·
Just for fun, I've tried that with the OSX calculator (in El Capitan, in case that matters). When I paste the number in the article (17281580835365214242) into
by loopbit 11y ago
Just for fun, I've tried that with the OSX calculator (in El Capitan, in case that matters).
When I paste the number in the article (17281580835365214242) into it, it shows as 9223372036854775807. Typing it by hand does the same, when you enter the last digit it transforms into that number, which is 0x7FFFFFFFFFFFFFFF in hex.
Funnily enough, if I paste the hex value (EFD4823541245822) and transform it to dec, it shows as the correct number, the one you can't paste or type.
So, the OSX calc looks broken too, in an even weirder way.
edit: Forgot to mention this was in programmer's view. As far as I can tell, other modes work fine.
- sergj 11y agoWorks for me after copying and pasting 17281580835365214242 it shows: 1,72815808353652E19
- dom96 11y agoIt seems that all calculator GUI apps bundled with any OS are in some way broken. I also find many of them inconvenient, for example the OS X calculator doesn't clear when I press the backspace button (I just figured out that the C key does this...).
- function_seven 11y agoI just messed around with it, and it appears to treat the 64-bit word as signed, and refuses to go past 0x7FF... So I figured I'd do some subtraction, but that just always answers with the same 0x7FF... value. Weird indeed, that it allows you to access everything above 0x800... in hex mode, but not in decimal mode.
- userbinator 11y agoThat's certainly unusual behaviour, since the parent says you can convert the value from hex to dec and it will show the correct unsigned decimal value. One thing programmer mode really needs is a signed/unsigned option when converting between bases.