Skip to content

All articles

← Knowledge Base

  1. Can lint recursively scan sub directories for the source code? For example, I want to use: lint Z:\*.* and have it then recurs down our directory structure and parse all our source files?

  2. How can I extend the properties of assert() to another function?

  3. How can I get PC-lint to support inline-assembly for the DIAB DATA C++ compiler?

  4. How can I tell lint to ignore my embedded SQL code?

  5. How can I torture test my code to achieve maximum reporting?

  6. How do I get lint set up to recognize that new can return a NULL if it fails to allocate the class?

  7. How do I run PC-lint from inside Microsoft Visual Studio?

  8. How do I suppress a message for a specific symbol? function? macro?

  9. How do I tell lint not to complain about my compiler headers?

  10. How do I tell PC-lint Plus where to find my compiler headers?

  11. How do I update PC-lint Plus or determine the newest version available?

  12. I want to suppress an error, such as 715, for C files, but not for C++ files.

  13. Is there a trial/evaluation version of PC-lint Plus?

  14. MISRA checking without an analysis of library headers

  15. My compiler in-line assembly begins with "#pragma asm" and ends with "#pragma endasm:. Can lint handle this?

  16. My lint error suppression is not working.

  17. What is a library header?

  18. What version of lint am I running?

Feedback and Knowledge Base

(thinking…)