how do I master the usage of pointers?
 It's All Fucked Shirt $22.14 |
 Shopping Cart Returner Shirt $21.68 |
It's All Fucked Shirt $22.14 |
how do I master the usage of pointers?
how do I master the usage of pointers?
It's All Fucked Shirt $22.14 |
Shopping Cart Returner Shirt $21.68 |
It's All Fucked Shirt $22.14 |
>how
Above fridge IQ.
Is this real?
Yes.
There's also a defcon video. Just check it out on YouTube.
it looks more like her skirt collapsed, exposing her crotch area
hot
Read haking the art of exploitation 2nd edition
They talk about pointers a lot
https://pointerpointer.com/
that site is literally tens of thousands of lines of javascript code. amazing.
That is just React being React, welcome to the modern web.
The developer only wrote a couple hundred lines locating your cursor to a grid and displaying an image which points towards that grid position.
Wtf
There's nothing to master in pointers, pointers are literally addresses of memory, idk what you see is complicated in that, whenever you need the value/content in that memory address you de-reference it using the asterisk *, that's all there is
Additionally, double pointers are pointers that point a place in memory where a pointer is stored and it's the same for triple pointers ....
more pointers memes
Thanks, i finally understood pointers
welcome buddy, we are here for each other
I think you meant: for each and everyone.
No
Better photo thanks to waifu2x
I would rather have lost information than "restored" information that isn't the original.
All you're doing is making it harder to find the original because you'll have to sit through a ton of AI upscaled slop of similar sizes and quality.
What is that merchant in the upper right corner
thought the asterisk was for declaring pointers. And what’s the &
The ampersand gives you the address, when you're dealing with an already "dereferenced value" (a regular variable)
the use of the asterisk in C is completely moronic, since the asterisk can mean either DEREFERENCE operator, or pointer (aka REFERENCE) type, depending on where it is.
by writing C code
Shitalians are so fricking ugly.
you just dereference an address in memory and what is used in the operation si what is stored at the line of addresses the size of the type of the pointer starting from the address in the pointer and going up.
>multi-dereferences
they dont even exist machine code but its just
>look to address, read 8 bytes of values, look at the address they point to
etctec
morons, please stop programming right now and do something useful, we are full.
queen of IQfy. laurie is love.
>queen
Uhhhhh
Perfect
He's cute.
Name?
I was going to learn how to use them, but I didn't see the point.
Not funny at all. Didn't laugh. Kys.
>pointers
obsolete tech
use C++ or Rust
>C++ doesn't have pointers
We still have pointers in Rust, Anon.
In French pointeur means a pedo rapist
so half of your country today
where is IQfy in that?
go leave
Only after you go back to India
I'm not from india friend
I'm french and I learn this word only like 2 years ago, many years after I knew what pointers were. I bet "pointeur" is a new zoomer meme word.
Pointeur is argot. Gtfo Jean-Hippolyte
>Hippolyte
lel, as if anyone with that name came here
>M...M...MUH POINTAAAAA
>all 32 bit addresses
>all aligned to 2 bytes
What kind of fricking game is this, anyway?
wouldn't int ** point at int ?
No because it's a pointer to a pointer, so it's an integer that contains the address value of another integer value that points to an integer.
>that soft looking hair and sweater
she's so perfect bros.
>she
lol
Don't forget the soft looking adam's apple
this meme series always irritates me because it conflates the type with the value. he should be pointing to a number with 'int' written above it.
soul
Read this:
http://cslibrary.stanford.edu/102/PointersAndMemory.pdf
If you still don't understand pointers after reading it, you're moronic and we can't help you.
Pointers are just indexes
Thing of the memory of your program as just being a giant array of bytes
And pointers are just indexes into that array that refer to different width chunks depending on the pointer type
So an int* refers to the starting index of series of bytes in the array big enough to store an int
you will never ask about pointers again after watching this video
8m
Pointers in C / C++ [Full Course]
3h47m
Or if you prefer...
The Pointer Sisters - Jump (For My Love)
>viral marketing
what the frick is even being marketed I'm not getting anything out of this "viral marketing" thing whatsoevermore
Juicy, throbbing, vascular girlwiener.
Learn assembly(x86, get a good book don't just learn an instruction set) then program in C. Practice DSA with C using pointers inverting binary trees n shieeeeet. Then make something.
also, DAS A MAYNEEEE
They're just numbers representing addresses.
What confused me for an embarrassingly long time was the arithmetic, then I realized that the `+ 1` for a pointer wasn't the same as the normal `+1`.
>the pointer it’s a number representing an address
>adding the ampersand gives you the address
Which is it
The address is a number.
A variable, say an int, is a number stored at an address.
The pointer is a variable, say a size_t, that stores the number of the address of the other variable.
Pointers to pointers are never needed. Prove me wrong.
Linked list.
I feel like it's the C syntax that trips people up, not actually the pointers. At least that was the case for me a long time ago when I first learned about pointers.
Imagine you have an array
A pointer is an item in the array that holds the index to another item in the array
A double pointer is an item in the array that holds the index to the other pointer.
The array is your memory.
Nothing in this thread explains why you would want a memory address.
it's like a soft link in a file system
To modify things in place instead of creating a copy.
To pass large objects to functions efficiently.
To work with dynamic allocations.
pointers are not particularly interesting or useful
I just keep adding ***'s and &&& to things until shit work
by not being a moron. for frick's sake, this shit isn't hard
Use them.
The idea of pointers is straightforward as frick. The only reason you're confused is because you don't use them often enough.
why does she have such vacant look in her eyes? it's creepy.
it's the brown eyes. Most people with brown eyes look like like that. hers are even lighter shade of brown.
Oh my god I hate Lily's voice. It's like a meme
>'ello guvna!
tier accent.
Woops, wrong tab.
why would you use pointer? do they use less resources when you invoke them instead of using the variable directly?
You could avoid pointers by passing back and forth the entire state of the program as an argument like those functional frickwits
I'm sure copying gigabyte of memory on each function call is an acceptable sacrifice in exchange for never having to learn how to manipulate memory correctly
Use a language that makes them less confusing, like Forth.
There's something a little bit off about her. I mean she looks conventionally attractive but...
Chances are you already know how it works, it's just pointer declaration in C is moronic so no need to beat yourself up over it.
Learn assembly then realize storing shit in the stack was surely a bad idea.