On Sun, Feb 16, 2020 at 7:53 AM Bruno Haible <br...@clisp.org> wrote: > > ... > > I agree, I would like to be able to explicitly release the memory. But > > I can't see any API to do that in fstrcmp.c. Is this one ok? > > The GNU Coding Standards [1] tell us to not worry about this situation. > However, > the alternative - to check for a memory leak - would be to run the test in a > loop (e.g. 1000 times), which is not practical since bison tests take some > noticeable time to execute already when executed once. Therefore, I'm OK to > look at a workaround.
The coding standard is wrong in this area. The practice breaks testing. Every time someone brings up failed acceptance tests or audits someone quotes the coding standard saying its OK. What more evidence do you need to realize the coding standard is broken? Jeff
