Hi Hannes, On Thu, 27 Apr 2017, Johannes Sixt wrote:
> Am 26.04.2017 um 22:19 schrieb Johannes Schindelin: > > I recently registered the git-for-windows fork with Coverity to ensure > > that even the Windows-specific patches get some static analysis love. > > > > While at it, I squashed a couple of obvious issues in the part that is > > not Windows-specific. > > Thanks for the fish. I'd looked at the series and had a few comments. > > Hunting memory leaks is the way to insanity. I hear you. Loud and clear. > Never again am I going to help with this. Awww? And here I thought I had your attention... *sniffle* ;-) > I prefer to rewrite this codebase to C++ and have leak-free code by > design. I had the pleasure of working with some software developers in 2004 who were experts at introducing memory leaks into C++ code. The same bunch of people later produced Java code that sorted a string list in cubic time (carefully avoiding java.util.Collections.sort(), of course). For every fool-proof system invented, somebody invents a better fool. Ciao, Dscho
