Programmer Humor

32495 readers

272 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

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

309

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

submitted 8 months ago by aggelalex@lemmy.world to c/programmerhumor@lemmy.ml

15 comments fedilink hide all child comments

all 16 comments

sorted by: hot top controversial new old

[–] P1r4nha@feddit.de 30 points 8 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?

[–] aggelalex@lemmy.world 16 points 8 months ago* (last edited 8 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.

[–] P1r4nha@feddit.de 8 points 8 months ago

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

[–] observantTrapezium@lemmy.ca 7 points 8 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.

[+] RagingHungryPanda@lemm.ee 2 points 8 months ago* (last edited 5 months ago) (1 children)

[removed by mod]

[–] P1r4nha@feddit.de 6 points 8 months 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 8 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.

[–] P1r4nha@feddit.de 2 points 8 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.

[–] lowleveldata@programming.dev 17 points 8 months ago (1 children)

It's my property tho

[–] Jordan_U@lemmy.ml 1 points 8 months ago

this

[–] desmosthenes@lemmy.world 16 points 8 months ago (1 children)

it’s not monospaced; my eyes

[–] aggelalex@lemmy.world 10 points 8 months ago

Peak shittiness requires sacrifice

[–] Hupf@feddit.de 16 points 8 months ago

CriminalScrum

[–] ooterness@lemmy.world 9 points 8 months ago

STOP! You have violated the law. Pay the court a fine or serve your sentence. Your stolen goods are now forfeit.

[–] Annoyed_Crabby@monyet.cc 9 points 8 months ago

Right to remain silent isn't granted to criminal scum, they have to either pay the court a fine or serve their sentence, and their stolen goods are now forfeit.

[–] lily33@lemm.ee 8 points 8 months ago

I see there an access violation...