At thus point I would like to see: - A release - Go through JIRA and fix issues - A release
We can update to Java 6 to allow the project to be built by Java 9 at any time, no big deal IMO. Crud, the oldest Java I have installed is Java 6. Hm, I'll push out Java 6 as the req and get that out of the way. Gary On Mon, Jul 17, 2017 at 11:19 AM, Simon Spero <sesunc...@gmail.com> wrote: > On Jul 16, 2017 11:49 AM, "Matt Sicker" <boa...@gmail.com> wrote: > > C quality somewhat depends on which version of C you're trying to remain > compatible with (I'm guessing C89 due to Windows, though I could be wrong). > Valgrind and other tracing tools are typically used. > > > Valgrind is a default choice (though then you still have plenty of > configuration choices to make :) > > A similar set of functionality is available using the various sanitizers > available in clang (and recent versions of gcc, though I haven't tried > that). These are described in the clang user manual: > > http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation > > Clang also supports static analysis, which can, um, detect errors > statically. This can sometimes generate a bunch of false positives, > depending on the coding style. The analyzer typically produces an html > report. These analyzers can be run using scan build. > > There are quite a lot more static analyzers available via clang-tidy, which > may or may not require installing an extra package. > > CppUnit is a sensible choice for unit tests, but does require that tests be > written in C++, which might be a problem if you are sent back in time (tip: > write to Bjarne at AT&T Bell Laboratories, and ask for a tape). >
