All articles ← Knowledge Base 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? How can I extend the properties of assert() to another function? How can I get PC-lint to support inline-assembly for the DIAB DATA C++ compiler? How can I tell lint to ignore my embedded SQL code? How can I torture test my code to achieve maximum reporting? How do I get lint set up to recognize that new can return a NULL if it fails to allocate the class? How do I run PC-lint from inside Microsoft Visual Studio? How do I suppress a message for a specific symbol? function? macro? How do I tell lint not to complain about my compiler headers? How do I tell PC-lint Plus where to find my compiler headers? How do I update PC-lint Plus or determine the newest version available? I want to suppress an error, such as 715, for C files, but not for C++ files. Is there a trial/evaluation version of PC-lint Plus? MISRA checking without an analysis of library headers My compiler in-line assembly begins with "#pragma asm" and ends with "#pragma endasm:. Can lint handle this? My lint error suppression is not working. What is a library header? What version of lint am I running?