> 0x4B2AC0AA is forty-eleven hexamillion, two hexahundred and tenty-twelve hexathousand and tenty-ten
Umm that's cool I suppose.
Mainly when I'm reading hex I'm looking for near-null, is it heap, stack or image memory? Those things are useful for me to be able to quickly distinguish and everything else is "calc.exe", "bc" or order-of-magnitude calculations based on number of bits. I do spend a lot of time reading hex, but I'm probably a numeric philistine.
Fourscore is a better fit, true. I'd disagree with nineteen though. French has fourteen, fifteen, sixteen, but then switches to a more awkward construction for 17-19. Fourscore and sixteen transitions to fourscore and ten and seven / fourscore and tenty seven.
(Note: Not saying it's awkward in an absolute sense, but in the context of a base-twenty system that method of constructing 17-19 fits badly)
An old TRS-80 assembly programming book I had suggested that an early conference of computer experts suggested that the last six digits be named actinium, barium, curium, dysprosium, erbium, and fermium until "cooler heads prevailed".
Umm that's cool I suppose.
Mainly when I'm reading hex I'm looking for near-null, is it heap, stack or image memory? Those things are useful for me to be able to quickly distinguish and everything else is "calc.exe", "bc" or order-of-magnitude calculations based on number of bits. I do spend a lot of time reading hex, but I'm probably a numeric philistine.