Re^5: When I see "10", I think:

Replies are listed 'Best First'.
Re^6: When I see "10", I think: by ikegami (Patriarch) on Mar 02, 2013 at 20:41 UTC
Which doesn't help you read the next 15 bits.	[reply]
Re^7: When I see "10", I think: by BrowserUk (Patriarch) on Mar 02, 2013 at 22:35 UTC
Which doesn't help you read the next 15 bits. That's all you got? You dig up an old thread to say: "Using octal for 16-bit values is that it isolates bit 15 nicely." And when you are shown that isolating the high bit in hex is trivial; you then say; "Oh, but it's not about the high bit; its about the other 15". Were you bored and just came looking for a argument? Well here it is. Translating hex nibbles to binary is child's play. Every programmer worthy of the name does in their head without thinking. The advantage over octal is obvious. (hint:byte alignment). With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^8: When I see "10", I think: by ikegami (Patriarch) on Mar 02, 2013 at 22:38 UTC
You didn't show how to isolate anything. Don't be an asshole once that's pointed out. Isolating in octal: `135753 => 1 35753` [download] Isolating in hex: `BBEB => 1 3BEB` [download] Not particularly hard, but it's still more work than the lack of it in octal.	[reply] [d/l] [select]


No such thing as a small change
	PerlMonks