Hello,
I'm sorry, but there is actually nothing planned for splint. As I'm doing the project on my own and I've not worked yet with splint, it will be unlikely that I'll write a parser for it. It was - well - first planned as an idea, before I used pc-lint, doxygen and unit-tests. For each parser it's not only parsing its output, but also the configuration - well and testing and I don't actually use C (without ++) any more and there is no splint for C++ AFAIK. For my part there are enough parsers, there are some things yet to do that are more important, I think - like documentation...
I suggest using pc-lint, which of course is not for free, but it's really very good and fast.
Best Regards
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes please I need the same thing.
splint is free and pclint is not free
Hello,
I'm sorry, but there is actually nothing planned for splint. As I'm doing the project on my own and I've not worked yet with splint, it will be unlikely that I'll write a parser for it. It was - well - first planned as an idea, before I used pc-lint, doxygen and unit-tests. For each parser it's not only parsing its output, but also the configuration - well and testing and I don't actually use C (without ++) any more and there is no splint for C++ AFAIK. For my part there are enough parsers, there are some things yet to do that are more important, I think - like documentation...
I suggest using pc-lint, which of course is not for free, but it's really very good and fast.
Best Regards
Michael