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??

[–] [email protected] 4 points 1 week ago* (last edited 1 week ago) (1 children)

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!

[–] [email protected] 1 points 1 week ago (1 children)

After the constructor?

No need for a destructir bc smart pointers?

Man you does not make any sense.

[–] [email protected] 3 points 1 week ago

Man your reading comprehension is really low.