4 ms·
Doing work that makes your library slower so that certain primitive memory checkers don't get upset doesn't seem like a good use of time to me. Especially when
by mikepavone 10y ago
Doing work that makes your library slower so that certain primitive memory checkers don't get upset doesn't seem like a good use of time to me. Especially when more sophisticated tools (Valgrind at least, probably others) can differentiate between actually leaked memory and stuff that's still reachable at program termination. Obviously there are scenarios where this is not appropriate, but it seems like a reasonable choice in many cases.
- ktRolster 10y agoIf your own code is clean other than de-allocating at exit, then I'm fine with that. If not, I'm asking you to kindly leave the industry, and not inflict your messy code on others.