2012-03-29 Yesterday, I took a look at cppcheck. [0] I've known it already for some time; came to it via Debian, because they analysis results of packages on their website. [1] Now I finally took a deeper look, set it up on my system and solved issues, reported by it. It is a tool, a great tool, like valgrind. A tool you should know how to use and actually use. There are lots of tools out there that assist you in producing quality code. One only needs to learn them ... and set them up for automated assistence. The latter is the next step to take for me. Well, cppcheck found a false positiv in my code. I was playing with pointers and it couldn't follow my pace, I believe. ;-) I reported this bug upstream. That was difficult, because I didn't wanted to register anywhere, and trac is a mystery to me anyway, and there was no mailing list address on the website. Eventually, I mailed to the email address of the most recent changelog entry in the upstream tarball. That went well. Now the bug is filed: [2] Finally, I also worked on mmh. Yesterday night, an idea occured to me ... That resulted in a small, but conceptionally wonderful change. It appears so obvious, now that I've done it. Let me in- troduce: The trash folder. :-) [0] http://cppcheck.sourceforge.net/ [1] http://qa.debian.org/daca/cppcheck/ [2] http://sourceforge.net/apps/trac/cppcheck/ticket/3691 http://marmaro.de/lue/ markus schnalke