Re:How Objective-C messaging works
by nonchalance on Saturday August 03, 2013 @10:32PM
(#6154345)
I stopped reading when I saw `i = 0xreadbook` and `typdef`. There are typos and there are fundamental misunderstandings -- not sure where these lie
Re:How Objective-C messaging works
by tomjakubowski on Saturday August 03, 2013 @08:30PM
(#6154004)
I'd probably avoid 0xB16B00B5.
I'd probably multiply and sum...
That's a bit overpedantic. It's a mnemonic for remembering the way the bytes are arranged in memory: "Ok, Bo: add re".
Nobody complains that r, o, y, g, b, i, and v aren't actual colors, do they? Other than you, I mean.
r=red, o=orange, y=yellow, etc.. No problem there.
What does K equal in hexadecimal? Well, it isn't defined for hexadecimal. K=20 is only defined in Base 21 and above.
Other than me? Hah, nice cheap shot, pole ;-)
The letters need only illustrate the positions and be memorable. No hex is required for this purpose.
Edit: The 0x communicates that the mnemonic is illustrating base 16, so your objection below is not valid.
Endian-ness changes when the base changes. For a clear explanation, actual hex is needed.
Try 0xDEADBEEF,0xBAADF00D, or any constant listed here: http://en.wikipedia.org/wiki/Hexspeak