v0.7.0

[lawmurray]

• Adds an experimental doxide cover command that outputs gcov-compatible JSON to enumerate executable lines in the source code. The intended use is to mix this line data with execution data from gcov for more accurate C++ code coverage reports, addressing the problem of uninstantiated function templates being ignored by code coverage tools.
• Minor improvement to extraction of brief descriptions (Improve detection of brief descriptions #52).
• Minor fix for presentation of macros (Multiline macros may include an end-of-line backslash when presented #53).

---

This discussion was created from the release v0.7.0.

[lawmurray]

For those interested, I've posted to my blog on the new doxide cover command and the motivation behind it: Improving C++ Code Coverage with Gcov, Gcovr and Doxide.

Generally, I've been motivated to improve my tooling around code coverage for C++, as the omission of function templates has been a longstanding issue for me that often produces misleading coverage reports. I'm aware of a couple of alternative solutions to the problem, but getting the required function template line data out of Doxide's existing parse was low hanging fruit, thus my experimentation with this.

I'm contemplating whether a source browser with code coverage information would be a useful (optional) addition to Doxide output, aiming more at internal developer documentation rather than external user documentation. Feedback on the usefulness of that is welcome.

[lawmurray]

Sneak peek of what I've been working on with respect to code coverage reports.

[lawmurray]

Code coverage reports are now available in v0.8.0! See the demonstration for a live example based on Doxide's own code and the documentation on how to get set up with your own codebase.