Johannes Schindelin <johannes.schinde...@gmx.de> writes: >> Hmph. I find a "leak" of a resource acquired inside the main >> function and not released when the main function leaves a lot less >> interesting than the other ones this series covers. > > Ah, I missed that this falls squarely into the "one-shot programs are > allowed to be sloppy in their memory management, essentially using exit() > as garbage collector" category.
I actually think it was a good intention of yours and I would agree with the patch. The automated tools that find and complain about these issues do not know about our local house rules like "do not bother freeing immediately before exit" and will keep notifying us of leaks. One way to reduce the noise level so that we can focus on real issues they may find for us in the future is to squelch these "uninteresting" ones by "fixing" them, even if our local house rule says OK, like this patch does. I said "a lot less interesting" and did not mean "it is bad for our code to do this". Thanks.
