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.
So, googling it, the general premise is you should use smart pointers instead to avoid crashes. Got it.
Uh
I think I’ll just let the cat drive instead
Smart pointers implies C++, which is not the right answer.
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
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.
But… per-process-isolation is a hardware feature, no?
So you really should implement it in your compiler so you don’t contravene it
Sure, that may be (it’s definitely not in userspace). But don’t forget it works by crashing your program.