130

The C++ experience (lemmy.world)

submitted 1 week ago by qaz@lemmy.world to c/programmer_humor@programming.dev

14 comments fedilink hide all child comments

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

[-] MyNameIsRichard@lemmy.ml 3 points 1 week ago

Yeah the compiler generates it so it's always there

[-] Valmond@lemmy.world 5 points 1 week ago

Well yes, except when you allocate stuff in the constructor.

[-] MyNameIsRichard@lemmy.ml 4 points 1 week ago

The compiler will still generate one. It won't be any use but it will be generated :)

[-] Valmond@lemmy.world 1 points 1 week ago

Well no because if you allocate stuff in the constructor, you are going to write a destructor now, freeing that allocated stuff up / closing that socket, pipe whatever etc.

Right?

Right??

[-] MyNameIsRichard@lemmy.ml 4 points 1 week ago* (last edited 1 week ago)

If I do it straight after the constructor, then definitely but if I get distracted by something else then it's only probably until I run it through valgrind and see the leak. These days, I mostly use smart pointers in new code though so there are fewer opportunities to need a destructor. It's funny that I never forget when opening a file or db connection!