News for hackers. Stuff that matters.
Re:How Objective-C messaging works by austinz on Saturday August 03, 2013 @07:44PM (#6153854)
What is "0xreadbook" in the context of a 32-bit int supposed to mean? Is the author just trying to be cute, or is this some sort of nonstandard representation of hexadecimal digits that I need to read up on?
Re:How Objective-C messaging works by orta on Saturday August 03, 2013 @07:50PM (#6153872)
It's the author being cute I think. I've never heard of it either.
Re:How Objective-C messaging works by tdd1 on Saturday August 03, 2013 @07:52PM (#6153878)
Yes dude,

it just an example hexadecimal representation. Don't take everything so literally...

Re:How Objective-C messaging works by aa0 on Saturday August 03, 2013 @07:58PM (#6153900)
Literally? A tutorial for noobs should be literally accurate -- throwing around non-proper representations is just a cloudy lazy explanation.
Re:How Objective-C messaging works by tdd1 on Saturday August 03, 2013 @08:05PM (#6153915)
appreciate, don't hate
Re:How Objective-C messaging works by to3m on Saturday August 03, 2013 @08:23PM (#6153975)
It's a reasonable comment. I got to "0xreadbook" and found it rather difficult to continue. If you're trying to explain stuff, you need to get these things right. You wouldn't provide something like "LET STORE OF VALUE X CONTAIN LITERALLY 15 AS INTEGER" as example C code, right? Because it's not even C. In fact it's just nonsense. So I fail to see why "0xreadbook" is a valid example hex value... because it's not even hex.

Bizarrely, despite the author's apparent confusion about this basic concept, the rest of the piece seemed kind of OK, and he even got the hex representation of 1.f correct.

A much better example hex number is 0x12345678. Every digit is different, and it's actually a valid number.

Re:How Objective-C messaging works by aa0 on Saturday August 03, 2013 @08:19PM (#6153960)
Appreciate misinformation? No thanks.
Re:How Objective-C messaging works by taspeotis on Saturday August 03, 2013 @08:34PM (#6154015)
it just an example hexadecimal representation

It's not hexadecimal, so what's your point?