Programmer Humor

31998 readers

788 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 5 years ago

MODERATORS

[email protected]

313

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

submitted 6 months ago by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

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

[–] [email protected] 31 points 6 months ago (2 children)

Horrible code. First, it doesn't compile because there's no ; at the end of the class definition.

And then more importantly you have a private destructor which means this CriminalScum's destructor will never be called, so you can't charge it with distruction either. Or are you telling me this CriminalScum has friends?

[–] [email protected] 16 points 6 months ago* (last edited 6 months ago) (1 children)

There's always an accomplice in crime.

Also, tall order to expect me to run and test a code written only for a shitpost.

[–] [email protected] 8 points 6 months ago

You're charging the class for a thought crime!!

[–] [email protected] 7 points 6 months 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.

[+] [email protected] 2 points 6 months ago* (last edited 3 months ago) (1 children)

[removed by mod]

[–] [email protected] 6 points 6 months ago (1 children)

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

[–] [email protected] 1 points 6 months 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.

[–] [email protected] 2 points 6 months 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.