3 ms·
I don't know why you're getting downvoted. It's likely something like malloc('HTTP') // note the single quotes or const char* s = "HTTP"; malloc(*s); Also
by underdeserver 3y ago
I don't know why you're getting downvoted.
It's likely something like
malloc('HTTP') // note the single quotes
or
const char* s = "HTTP";
malloc(*s);
Also I would expect the string to be reversed if she's working on a little-endian system (which the most common ones today are, including Intel 64 bit and ARM64).
- jraph 3y ago> I don't know why you're getting downvoted. I didn't, but probably because they may read like they are lecturing Rachel. Which looks bad in itself, but feels extra ridiculous for anyone familiar with Rachel's blog. She pretty much knows how malloc and C work. She probably could write her own malloc without sweating. Worse still, OP is seems to try to imply that Rachel is trying to lie and brag about some irrelevant gift (decoding hexadecimal in her head) by making up examples. Let's just say that it's not very charitable and it's also against HN guidelines. OP could just have expressed their surprise and asked for some clarification instead. They are not reading "is really" correctly and not considering that Rachel is taking some shortcuts so the article remains simple and enjoyable to read, as most good writers do, which in the end makes OP's whole comment somewhat moot. See abbeyj's reply for more context. The full explanation is in Rachel's article abbeyj points to, there's no need to guess. edit: I had skipped the last line of OP's comment. It's just outright mean. No wonder they are downvoted actually.
- underdeserver 3y agoI skipped that last line too. Thanks for pointing it out. I now do know why they're being downvoted.