Programmer Humor

33716 readers

1329 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.

founded 3 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

552

Pointers explained: (lemmy.world)

submitted 4 months ago by ZILtoid1991@lemmy.world to c/programmer_humor@programming.dev

77 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Sylvartas@lemmy.dbzer0.com 10 points 4 months ago* (last edited 4 months ago) (1 children)

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)

[–] DahGangalang@infosec.pub 4 points 4 months ago

Another reason I commonly see: to change the structure / "main pointer" to a data structure (esp during freeing and cleanup).