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?
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
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.
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?
There’s always an accomplice in crime.
Also, tall order to expect me to run and test a code written only for a shitpost.
You’re charging the class for a thought crime!!
Also, if I’m not mistaken the uninitialized
propis not guaranteed to benullptrhere, so this private destructor could be trying to free from some random pointer.wait, in C++, if you don’t assign the value to that pointer, it’ll be whatever happens to be at that block of memory of something!?
Yep, variables that are merely declared are not initialized, so their value is not guaranteed. Could be anything.
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.
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.