News for hackers. Stuff that matters.
Re:Comparing C and C++ usage and performance with a real wor... by matthewaveryusa on Sunday September 03, 2017 @02:34PM (#15163020)
My experience has been the opposite of yours. Freeing is always a good idea so you can use tools like valgrind to find memory bugs without needing to sort through all the false positives. Your short-lived program today can become a service tomorrow. c++is worth it just for RAII
Re:Comparing C and C++ usage and performance with a real wor... by wilun on Sunday September 03, 2017 @02:40PM (#15163054)
Valgrind does not force the user to read mem leak reports along errors. Actually IIRC, by default you don't get detailed leak reports.
Re:Comparing C and C++ usage and performance with a real wor... by matthewaveryusa on Friday September 08, 2017 @09:25AM (#15199957)
True, the defaults are pretty lame, but my point is if you don't free, and you start using data you intended to free, that's a memory bug valgrind won't be able to help you with unless you free your memory.

FWIW, this is in my bashrc along with a myriad of other programs that have lame defaults: alias valgrind='valgrind --leak-check=full --show-reachable=yes --track-origins=yes --track-fds=yes --error-limit=no'