Pointers explained:

Nah, she's 5 or younger. She lied about being 6 (school age) to get adopted. It's a very wholesome story (if you disregard the war, political intrigue and terrorism).

🙄

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.

What's the * for again?

Considering that most of the "answers" I've found on StackOverflow were complete dogshit, I'm wary of this reading list

Sure, that may be (it's definitely not in userspace). But don't forget it works by crashing your program.

So you really should implement it in your compiler so you don't contravene it

This Sparta C. We live for danger.

In the C programming language. Or do you mean which C project specifically? Because as Technus surmises in their response, it's usually a better idea to set up aliases (typedefs or heck, even #defines) so that you're offloading some of the mental strain keeping track of the layers, and that's likely to be what happens in production code.

But the underlying data type is still T***.

if you're working with higher level languages you pass-by-reference all the time. give a list to a function to modify it? that's by reference. giving an event handler function to a framework? that's by reference. setting a property on an object? that's usually by reference.

Most of the time you pass by reference for more outputs, or by const ref to avoid copying a big-ass data structure (which is not always straightforward, with structures smaller than a pointer, which are pretty big in 64 bits architecture, you lose more to the ref overhead than to the copy IIRC)

Reference values are quite useful, such as:

double valOut;
if (parseDouble(valOut) == 0) { //Argument of parseDouble is ref type, no & needed for input, no exceptions needed for error handling
    [...] //No error, code executed normally
} else {
    [...] //Erroreus input
}