One of the issues we have is commenting. When something is not a defect in the code, for an example. Adding a comment for that line, or if the comment has two or three lines, it can be difficult. Simulating a real-time operating system and firmware can be quite difficult if you're doing multiple threading in different entry points. If you're not using the same macros for critical sections, it can also be a little bit tedious to get around. I would like to see better command-line tools that we can interface it with. We would like to see support for a continuous integration build environment. The reports in this solution could be made cleaner.
I would like to see improved support for annotating "Not a bug" in the source code. Currently the line itself has to be annotated which can result in very long line comments. Which if coupled with doxygen becomes somehwat odious. This was also found to be somewhat buggy at times. Support for AUTOSAR C++14 is something that I would like to have.
One of the issues we have is commenting. When something is not a defect in the code, for an example. Adding a comment for that line, or if the comment has two or three lines, it can be difficult. Simulating a real-time operating system and firmware can be quite difficult if you're doing multiple threading in different entry points. If you're not using the same macros for critical sections, it can also be a little bit tedious to get around. I would like to see better command-line tools that we can interface it with. We would like to see support for a continuous integration build environment. The reports in this solution could be made cleaner.
I would like to see improved support for annotating "Not a bug" in the source code. Currently the line itself has to be annotated which can result in very long line comments. Which if coupled with doxygen becomes somehwat odious. This was also found to be somewhat buggy at times. Support for AUTOSAR C++14 is something that I would like to have.