12 Sep
2012
12 Sep
'12
9:40 p.m.
Tim Ruehsen tim.ruehsen@gmx.de writes:
As Simon Josefsson made clear, the main reason are automated tests for memory leaks using valgrind. Something, that a library test suite should not miss.
...
But without freeing resources in main(), you now can't easily say, if you have a problem in the library or in the testsuite.
However, as far as I recall, the Nettle library does not contain any calls to malloc or other memory allocating functions. So I don't think there could be any memory leaks from the library?
If it is a huge effort to release memory from the testsuite, it may not be worth it. But if it is a small effort, and it leads to being able to run all the testsuite under valgrind without any warnings, I would support doing it.
/Simon