>just dedicate 4 hours of your life to learn pointers bro
Just dedicate 4 hours of your life to learn pointers bro
Other urls found in this thread:
open-std.org
myredditnudes.com
twitter.com
why do you need 4 hours to understand pointers
>he got filtered by computer memory
>just dedicate 30 seconds of your life to learn pointers bro
>wow maaaan 4 hours is like a lot
>just imagine how much porn I can watch instead
>C/C++ in 2022
lmao stay poor
ok, not every language has pointers, but every reference has indirection, which is the only "hard" part about pointers. if you dont understand indirection you cant be a real programmer, it's that simple.
4h is nothing for such a fundamental concept you'll know all your life.
kek I made the original image, it's always fun to still see it being shared
Rust doesn't have this problem.
This! So much this! Rust will fucking DEPRECATE C/C++, can I get an amen Rust sisters?
pointers "point" at a location in memory. What's so difficult to understand about it?
Rust references are the same thing as C pointers, but gimped.
what is a pointer? Is it same as a reference to a memory sequence?
is an javascript object something like a "pointer"?
I like pic related better
>Recently got hired as a C programmer
Feels good man.
4 whole ours? Bro I can't do that. I have tik toks to watch.
It took me a week when I was 18
Javascript uses pointers for every object implicitly, yes. That's why
let obj = {};
let obj2 = obj;
obj.msg = "Hello";
console.log(obj2.msg);
Works.
In C all references have to be explicit and = makes a copy of the data instead of a copy of the reference. That's one thing pointers are for.
I actually think you'd be hard pressed to comprehensively cover pointers in 4 hours. You'd have to go over:
>the basics
>reading the retarded declaration syntax
>alignment
>aliasing (incl. strict aliasing and restrict)
>volatile
>arithmetic and comparison (incl. all the possible UB) and relation to arrays
>function pointers
>provenance
But I'm sure that's not the content of this video. It probably spends most of its time covering pointer-adjacent topics like stack and heap and implementing some linked data structures.
what is a pointer?
>>provenance
huh?
Nothing to it.
And that's a good thing.
>They may also treat pointers based on different origins as distinct even though they are bitwise identical.
That's fucked up.
>what is a pointer?