Reto Schneider
Reto Schneider
Excerpt from the [LLVM Coding Standard](http://llvm.org/docs/CodingStandards.html#file-headers): > A few things to note about this particular format: The “-_\- C++ -_-” string on the first line is there to tell Emacs...
It would be nice to have an easy way to invoke [include-what-you-use](http://include-what-you-use.org/).
This plugin prints the MISRA C++:2008 rule headlines as diagnostic messages and therefore does not follow (at all) the best practices given here: http://clang.llvm.org/docs/InternalsManual.html#the-format-string How to improve this?
I tried to integrate [Coverity scan](https://scan.coverity.com/) into the Travis build and failed badly. Coverity complains about less-than-85% units being compiled when simply building clang-misracpp2008. When trying to build the whole...
Exactly zero speed optimization has been done so far. For daily usage the performance needs to be improved greatly.
All except the clang-tidy binary could/should be cached between builds. Travis CI has specific support for [this](http://docs.travis-ci.com/user/caching/).
Migrate all existing checks from [clang-misracpp2008](https://github.com/rettichschnidi/clang-misracpp2008/) to this project.
When comparing license compliance software systems such as [FOSSA](https://fossa.com/product/open-source-license-compliance), [Mend](https://www.mend.io/open-source-license-compliance/) (formerly WhiteSource), [Black Duck](https://www.synopsys.com/software-integrity/solutions/open-source-security.html), etc., one big difference is that FOSSology seems to not have anyone offering commercial support and/or...
Nobody stepped up to assemble a new 1.0 based maintenance/security release. At the very least our users should know that.
While (again) not an official release, this will advance us by 205 commits: ``` $ git rev-list --count 178b945e5497b813b1239e2fbf57e34b7488745f..HEAD 205 ``` Smoke tested like this: ``` $ examples/client/lwm2mclient_tinydtls -h leshan.eclipseprojects.io...