2 ms·
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 o
by austinz 13y ago
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?
- orta 13y agoIt's the author being cute I think. I've never heard of it either.
- tdd1 13y agoYes dude, it just an example hexadecimal representation. Don't take everything so literally...
- aa0 13y agoLiterally? A tutorial for noobs should be literally accurate -- throwing around non-proper representations is just a cloudy lazy explanation.
- tdd1 13y agoappreciate, don't hate
- aa0 13y agoAppreciate misinformation? No thanks.
- to3m 13y agoIt'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.
- deleted 13y ago[deleted]
- taspeotis 13y agoit just an example hexadecimal representation It's not hexadecimal, so what's your point?