Programmer Humor

38363 readers

82 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 6 years ago

MODERATORS

cat_programmer@lemmy.ml

AgreeableLandscape@lemmy.ml

314

You have the right to remain silent (lemmy.world)

submitted 2 years ago by aggelalex@lemmy.world to c/programmerhumor@lemmy.ml

16 comments fedilink hide all child comments

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

[–] observantTrapezium@lemmy.ca 7 points 2 years ago (1 children)

Also, if I'm not mistaken the uninitialized prop is not guaranteed to be nullptr here, so this private destructor could be trying to free from some random pointer.

[+] RagingHungryPanda@lemm.ee 2 points 2 years ago* (last edited 1 year ago) (1 children)

[removed by mod]

[–] P1r4nha@feddit.de 6 points 2 years ago (1 children)

Yep, variables that are merely declared are not initialized, so their value is not guaranteed. Could be anything.

[–] waz@lemmy.world 1 points 2 years ago (1 children)

Correct me if I'm wrong, but I'm pretty sure some compiler settings can change this. I have a fuzzy memory of a bug that went away when compiled with debug flags enabled and the difference was that unassigned variables were being zeroed vs not zeroed.

[–] P1r4nha@feddit.de 2 points 2 years ago

Yes, actually at my job a co-worker just found exactly such a bug yesterday: Debug build zeroed out the variable and the release build didn't. So the bug only occurred in the release build, but could not be reproduced on the debug build where the developers work on. So in the end he found it because of the different compiler flags used for debug vs release builds at our work place.