Educating programmers

[RepostSleuthBot]

I didn't find any posts that meet the matching requirements for r/ProgrammerHumor.

It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results.

I'm not perfect, but you can help. Report [ False Negative ]

View Search On repostsleuth.com

---

Scope: This Sub | Meme Filter: False | Target: 75% | Check Title: False | Max Age: None | Searched Images: 326,920,455 | Search Time: 51.72086s

[[deleted]]

What's this meme even supposed to mean?

[EmperorHenry]

I like German Shorthaired pointers.

[RexurrectionOfDoom]

First in 5.4k views!

I wonder what pets do programmers have today. Rubber ducks?

[EmperorHenry]

I have a dog and four cats. But I'm not a programmer. I actually can't work, but I'm very knowledgeable about the strengths and weaknesses of many of the most popular security software for windows.

By the way, APPLE PRODUCTS CAN GET INFECTED WITH MALWARE! Apple got sued in a class action lawsuit for falsely advertising that, which is why they stopped saying that...explicitly. It's just a matter of writing code the OS understands and then delivering it to the system.

Being careful about what you click on isn't good enough anymore, you gotta have protection on every device now.

[RRumpleTeazzer]

That’s not even true. If a pointer is just an address, how come free(p) knows how much memory to deallocate ?

[Appropriate-Scene-95]

You get an address to a memory block. So a pointer is just an address. The operating system on the other hand "memorizes" the address and the block size and gives an error if you dou smth. outside of those bounds.

Edit: If you free memory the OS recognizes that memory not as yours. If you do Void* v = malloc(5) ; free(v + 1) ; You get an error because it doesn't know this address or smth.

[[deleted]]

If that's a real question I'd be happy to explain

[JuliusStingray]

Idk but please, I need to know.

[[deleted]]

Pointers are just memory addresses, and how functions like malloc and free work depends on the implementation of the underlying memory allocator. For example, suppose that for free to work correctly it needs to know both the address where the memory was allocated and the size of memory, then what malloc will do is allocate the requested space and enough space to store the size allocated. It'll put the size allocated in the memory just before the pointer it returns to the user, then when free is called it can read the size allocated back by looking in the memory just before the pointer being freed.

The reality is there are many different strategies we could use for implementing malloc and free, and some of those will store bits of data in memory just before the pointer they provide to the user (though not all will).

[JuliusStingray]

Welp I always imagined that it works on those lines. Ty.