All articles ← Knowledge Base After some of the error messages in your manual, you have numbers in square brackets. What do they mean? 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? Can you tell me which of my #include files are not used? Disable MISRA Checking for Library Files Do you support any of the checks from Scott Meyers' books? Help - I'm getting too many messages. Help - you don't have a compiler options file for my compiler. 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 suppress a message for a single file? -efile does not work. 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 get patches for PC-lint? for FlexeLint? How do I order an update? 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 lint where to find my compiler headers? I check for strict ANSI compliance for my C programs by using the -A option, but I don't want complaints about my C++ style comments beginning with // I have deeply nested includes and I'm getting message 322 (Unable to open include file) even through my paths are set correctly. I want to check for strict ANSI portability. Is there anything I should do in addition to the -A option? I want to inhibit all messages emanating from one of my files, but the -efile option is not working. I want to port from 32-bit to 64-bit code. I want to suppress an error, such as 715, for C files, but not for C++ files. I'm trying to suppress wrapup message 754 (Local Structure Member Not Referenced) with an in-line lint comment, and it's not working. I'm using PC-lint with VC++ Version 6.0. My lint messages start out formatted correctly, then suddenly they are formatted incorrectly. Is there a trial/evaluation version of PC-lint/FlexeLint? It's nice to have a pdf manual, but am I allowed to print it? Can I get the manual in book form? Lint complains about my in-line assembly 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. PC-lint (running under Windows or DOS) is giving me strange errors on code transported from UNIX. It doesn't seem to properly handle the Unix "end of line" characters? Redeclaration errors with Mixed C and C++ code The compiler that I use has "__asm__" as the in-line assembly keyword. Is there a way to tell lint to totally skip any code beginning with that and ending with a semi-colon besides using an "#ifndef _lint"? What is a library header? What version of lint am I running? Will lint work with my cross-compiler?