they used to call him the deref king back in college
post
Worse version of this


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. 🤷♂️
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
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.
I mean, that's pretty much what happens to me every time I try to use pointers, so the meme checks out.
Rumble Tumble Games in the wild
Didn't expect to see the Drift King here
as a python script kiddie, this is way over my head, but upvoted because of RT Game
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?
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
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.
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.
Now that explain the & part of the pointers that I never really understood.
The & operator references the value.
int i;
int* p = &i;
In C++, the & at the function argument makes it a reference type (safe pointer).
void someFunction(int& refVal) {
[...]
}
*x = dereference or "point to". Treats the variable x as containing a pointer value. Evaluates to a variable existing at the address in x.
&x = reference or "get address of". Evaluates to the address of x.
They're complimentary operators, so *(&x) cancels out and is equvalent to just x.
Am I a computer scientist now?
The placement of the labels is a bit sloppy but I think it tracks. The character in the middle (int*) is pointing at int, then the one on the left (int**) is pointing at the middle one (int*), etc
What I want to know: what is that shirt and where do I get it?


top 50 comments