they used to call him the deref king back in college
this post was submitted on 08 Jun 2026
485 points (94.8% liked)
Programmer Humor
31797 readers
178 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
Worse version of this
Null termination is no longer recommended, use fat pointers instead!
load more comments
(9 replies)
Wait. It’s been a long time but shouldn’t be int*** -> int** -> int* -> int ?
I think int*** is meant to be pointing at int**, but the image is just unclear about where everything is in perspective.
Pretty sure the image is clear:
int*** -> int*
int** -> int
Int* -> int
Clarity doesn’t mean correct. But that’s probably why it’s posted here. 🤷♂️
RT*** isn't pointing at RT*, he's pointing at the TV showing RT**. The fact you think otherwise is what makes the image unclear. I'm not sure why you insist on them being wrong.
load more comments
(1 replies)
int** is inside a TV, and persumably int* must be inside another TV(even though uts not edited in). The image perespective is showing one thing inside the other, inside the other. So when when int*** points the TV it reference int**, which reference int* which reference int. Its just edited very bad
load more comments
(6 replies)
I mean, that's pretty much what happens to me every time I try to use pointers, so the meme checks out.
yep this is just someone misunderstanding pointers lol
load more comments
(1 replies)
Didn't expect to see the Drift King here
Drift King? You mean Dan the Villain
Rumble Tumble Games in the wild
Seeing him break containment is wild
as a python script kiddie, this is way over my head, but upvoted because of RT Game
that's not LaurieWired
So, googling it, the general premise is you should use smart pointers instead to avoid crashes. Got it.
Smart pointers implies C++, which is not the right answer.
Unlike many other programming languages, which are often picked up on the go from tutorials found on the Internet, few are able to quickly pick up C++ without studying a well-written C++ book. It is way too big and complex for doing this. In fact, it is so big and complex, that there are very many very bad C++ books out there. And we are not talking about bad style, but things like sporting glaringly obvious factual errors and promoting abysmally bad programming styles.
https://stackoverflow.com/questions/388242/the-definitive-c-book-guide-and-list
Considering that most of the "answers" I've found on StackOverflow were complete dogshit, I'm wary of this reading list
Uh
I think I'll just let the cat drive instead
They all have footguns that cause different crashes.
If you want to do explicit memory access without inevitable safety problems, you need Rust. That's the whole hype with Rust.
load more comments
(2 replies)
Uh I'm a charisma class (with unfortunate base stats) what's int
It’s what makes mages turn those squiggly lines on paper into fireballs.
Not clerics though, they’re different.
Why should the left one in the rectangle be int**? It doesn't make sense to me, they are both clearly just int*
What am i missing?
I they're supposed to be pointing at each other but the edit didn't really work because his arm is pointing too far away
load more comments
(1 replies)
Real talk: is there any practical use-case for T*** of any pointee type?
Dynamically allocated multidimensional arrays.
Ah right, so that would be a 3D array.
T*is a single row ofTT**is a list of rowsT***is a list of "layers" in the third dimension
This would be incredibly hazardous to pass around as a bare pointer with no context, though. I'd expect to see this in a struct that, at minimum, also includes fields for the size of each dimension.
This ~~Sparta~~ C. We live for danger.
Tesseract Array
load more comments
(3 replies)
view more: next ›