[neomutt-devel] Analysis of NeoMutt
Richard Russon
rich at flatcap.org
Sat May 5 15:45:52 CEST 2018
Hi everyone,
A few weeks back Federico (@fekir) created a huge number of code
improvements based on 'cppcheck' (a static analyser). He documented how
he did it on a new developer page:
https://neomutt.org/dev/analysis
I've just filled out all the other ways and tools which we've used to
improve the code and debug NeoMutt.
- Clang-Format - Source code formatter
- Coccinelle - Source code manipulation
- Compiler - Enable gcc/clang warnings
- Coverage - Code coverage testing
- Coverity - Source code anaylser
- CppCheck - Source code analyser
- Cproto - Function prototype generator
- Ctags - Source tags generator
- Include-What-You-Use - Header file checker
- Scan-Build - Source code anaylser
- Travis - Continuous Integration
- Valgrind - Run time memory checker
Cheers,
Rich / FlatCap
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mailman.neomutt.org/pipermail/neomutt-devel-neomutt.org/attachments/20180505/be9722d9/attachment.sig>
More information about the neomutt-devel
mailing list