Technical Support FAQ - Page 2

1. How can I tell lint to ignore my embedded SQL code?
2. 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.?
3. 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?
4. I'm using PC-lint with VC++ Version 6.0.  My lint messages start out formatted correctly, then suddenly they are formatted incorrectly.
5. I'm trying to suppress wrapup message 754 (Local Structure Member Not Referenced) with an in-line lint comment, and it's not working.
6. I check for strict ANSI compliance for my C programs by using you -A option, but I don't want complaints about my C++ style comments beginning with //
7. I want to check for strict ANSI portability.  Is there anything I should do in addition to the -A option?
8. It's nice to have a pdf manual, but how do I get a printed paper manual?
9. After some of the error messages in your manual, you have numbers in square brackets.  What do they mean?
10. I am programming with VC++ and will have fragments of code that look like the following:
        class *a = new SomeClass;
        if(a !=NULL)
           delete a;
        ...
    Lint will return an error 774 expression always evaluates true!  How do I get lint set up to recognize that new can return a NULL if it fails to allocate the class?
11. I have deeply nested includes and I'm getting message 322 (Unable to open include file) even through my paths are set correctly.
12. How can I extend the properties of assert() to another function?
13. ASSERT() is causing "unreachable code" messages.  How can I stop this complaint since it is true only in the debug version of my code?
14. How can I tell lint about my compiler's sbit?
15. I want to suppress an error, such as 715, for C files, but not for C++ files.
16. I am using a C++ compiler from DIAB DATA.  An example of their in-line assembly is as follows:
       asm void refresh_watchdog(void)
       {
          move.b #$55,$0fffa27
          move.b #$0aa,$0fffa27
       }
    How can I get your lint to support this?
17. My compiler in-line assembly begins with "#pragma_asm" and ends with "#pragma endasm".  Can lint handle this?
18. 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"?
19. How can I exclude the Microsoft keyword " __uuidof" from elective note 1924 (C-style cast)?
20. I get Error Message 18 even though I suppressed it with -e18.

---

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

For SQL such as
     EXECSQL ... ;
use the options: 
     -dEXECSQL=_to_semi
     +rw(_to_semi)

for code such as
        EXEC SQL ... ;
use: 
     -dEXEC=_to_semi
     +rw(_to_semi)

2.  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.?

Use our +frb (Read Binary) flag to handle Unix files.

3. 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?

No, but what you can do is obtain a list of files using the DOS dir command such as:
   dir /s/b *.cpp > project.lnt
You can then use project.lnt as input to lint.  You should make sure that all those files are in the same project.

4.  I'm using PC-lint with VC++ Version 6.0. My lint messages start out formatted correctly, then suddenly they are formatted incorrectly.

The default message presentation is to not start with a location if it's a wrap-up message.  Using the option -hF will insist on location information always.

This option, as well as others appropriate for Visual Studio, is contained in env-vc6.lnt.  Place env-vc6.lnt after std.lnt on the argument line.

5.  I'm trying to suppress wrapup message 754 (Local Structure Member Not Referenced) with an in-line lint comment, and it's not working.

Because message 754 is a "wrapup message" it's not associated with any specific line of code.  You can suppress it with (for example):
     -esym(754,e2)
This will then suppress this message for ALL symbols whose names are "e2".

What we do , in our own code, is preface symbols that are unused with un_ as in un_e2.  We can then do a 
     -esym(754,un_*)

6.  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 //

For versions previous to 8.00i, use the option
    -"esym(950,//)"
(the double quotes are required within a .lnt files)
The // is part of the C99 standard, so beginning with version 8.00i, we will not complain about this construct, unless you use -A(C90) to indicate that you want C90 checking.

7.  I want to check for strict ANSI portability. Is there anything I should do in addition to the -A option?

Several years ago, we wrote ANSI C headers, as well as POSIX C headers, for inclusion with our FlexeLint product. They do not contain compiler-specific or library-specific function prototypes, macros, typedefs, or headers. The zipped headers are available from our web site. Go to our current Patch page for the links.

8.  It's nice to have a pdf manual, but how do I get a printed paper manual?

You have permission to print out one copy of the manual for each license that you have, however you may prefer to order a bound copy from OnDemandManuals.com in Canada. The cost is US$ 35 plus shipping.

9.  After some of the error messages in your manual, you have numbers in square brackets. What do they mean?

In our manual (and also in msg.txt ) we cross-reference some of our error messages to the bibliography reference that applies. In the case of message 1024, the reference is to Bibliography item 11 (which is the ARM), section 13.2. This is often times helpful for a further explanation of the message and possibly alternative coding options.

10. I am programming with VC++ and will have fragments of code that look like the following:
   class *a = new SomeClass;
   if(a !=NULL)
   delete a;
   ...
Lint will return an error 774 expression always evaluates true! How do I get lint set up to recognize that new can return a NULL if it fails to allocate the class?

Just use the option +fnn (turns on the new can return null flag)

11. I have deeply nested includes and I'm getting message 322 (Unable to open include file) even through my paths are set correctly.

We bend over backwards trying to accommodate all the varieties of operating systems and compilers, but sometimes we need some user help. If the number of nested files goes above the value of max_open (set by the -maxopen(n) option, we start closing earlier files before opening new ones. On the way back, we use fseek to find the correct location. Hence if maxopen is small enough, there should be no problem. However some libraries don't support fread'ing to files opened with "R". Therefore you can either raise the level of maxopen to something large like 100 or you can use +frb which will force the use of "rb" for the fopen call.

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

assert is normally a macro and doesn't come with built-in properties. We do provide a function that does have built-in assert-type properties whose name is __assert, so you would use
   -function(__assert,yourfunction)

13. ASSERT() is causing "unreachable code" messages. How can I stop this complaint since it is true only in the debug version of my code?

You are probably using ASSERT(0). PC-lint is trying to warn you that this implies that certain code will not be reached. You can fool PC-lint by using ASSERT(zero) where zero is a global variable initialized to 0.

14. How can I tell lint about my compiler's sbit?

I'm assuming sbit is a mask applied to a global register.  In that case, it's more like a bool than a char except we have to ignore initialization.  I'm assuming you don't assign to an sbit or if you do it's just a single bit.  If that's the case, you can use our _ignore_init reserved word as follows:
     +rw(_ignore_init)
     -d"sbit"=_ignore_init bool"

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

Use the -header option, as in:
     -header(x.h)
and then within the header file (x.h in this example):
     #ifdef __cplusplus
         //lint +e715
     #else
         //lint -e715
     #endif

16.  I am using a C++ compiler from DIAB DATA. An example of their in-line assembly is as follows:
asm void refresh_watchdog(void)
   {
   move.b #$55,$0fffa27
   move.b #$0aa,$0fffa27
   }
How can I get your lint to support this?

As you may have discovered, using the +rw(asm) option does not do the trick.  You need to use: 
     +rw(_ignore_init
     -dasm=_ignore_init
You will also need the -$ option.

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

Use:
   +pragma(endasm,on)
   +pragme(asm,off)
This is described in Section 5.8.6 of the manual.

18.  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"?

Try:
   +rw(_to_semi)
   -d__asm__=_to_semi
This option is discussed in Section 5.8.3 of our manual.

19.  How can I exclude the Microsoft keyword __uuidof from elective note 1924 (C-style cast)?

Look at co-msc60.lnt and you'll see that __uuidof is defined as follows:

     //  define __uuidof() and suppress Errors 50 and 69
     //  in exprs. containing same
     -d" __uuidof()= /*lint --e(50,69) */ (_GUID)0"

Just add 1924 and any other message number you want to suppress to the list.  You can either modify co-msc60.lnt or add it as an option to std.lnt after the reference to co-msc60.lnt

20.  I get Error Message 18 even though I suppressed it with -e18

If you are using winnt.h in any of its manifestations prior to Visual C++ Version 6 then you may have trouble turning off Error 18. You may also have trouble turning off Warning 624 even with a version of winnt.h as late as Visual C++ 6. Although winnt.h originates with Microsoft it finds its way into many other compiler's suite of header files such as those offered by Borland and Watcom.

Here is a run-down on problems introduced by winnt.h and what you can do about them.

1. Error 18 problem.

There is a sequence in early winnt.h files that goes as follows:

   /*lint -e18 */  // Don't complain about different definitions
                   // DWORD ExceptionCode;
   /*lint +e18 */  // Resume checking for different definitions

Clearly this should have been:

  /*lint -save -e18 */ // Don't complain about different definitions
                       // DWORD ExceptionCode;
  /*lint -restore */   // Resume checking for different definitions

Workaround:

If you are editing winnt.h , you can make the change cited above, or eliminate the lint comments altogether as Microsoft has done with their Version 6 of Visual C++.

If you do not wish to edit winnt.h (which is understandable) you can employ the option:

   -esym(18,Symbol-name)

where, of course, Symbol-name is replaced by a suitable name. This will suppress the error for the named symbol. Since the Symbol-name can contain wild-card characters you may even use:

   -esym(18,*)

2. Message 624

There is a pair of lines in all versions of winnt.h as follows:

   /*lint -e624 */
   /*lint +e624 */

This looks like an old effort to suppress a warning about a typedef being redeclared (to be something different) in another module. The effect, as in the case of Error 18 above, is to turn on Warning 624 even if it had been turned off.

If you are editing winnt.h you should delete both lines as they are clearly intended as a NO-OP.

If you are not editing winnt.h you can employ the option

   -esym(624,Symbol-name)

As in the case of Error 18 above, wild cards can be used to suppress all 624's as follows:

   -esym(624,*)

3. macro turn-on of Warnings 527 and 530.

There is a sequence of three macros that when used have the effect of turning on Warnings 527 and 530 even if they had previously been turned off:

 #define UNREFERENCED_PARAMETER(P) \
         /*lint -e527 -e530 */ \
    { \
        (P) = (P); \
    } \
         /*lint +e527 +e530 */
 #define DBG_UNREFERENCED_PARAMETER(P) \
         /*lint -e527 -e530 */ \
    { \
        (P) = (P); \
    } \
         /*lint +e527 +e530 */
 #define DBG_UNREFERENCED_LOCAL_VARIABLE(V) \
         /*lint -e527 -e530 */ \
    { \
        (V) = (V); \
    } \
         /*lint +e527 +e530 */

These macros exhibit the same problem that was exhibited in the earlier examples involving Error 18 and Warning 624. Clearly these should have been:

 #define UNREFERENCED_PARAMETER(P) \
         /*lint -save -e527 -e530 */ \
    { \
        (P) = (P); \ } \
         /*lint -restore */
 #define DBG_UNREFERENCED_PARAMETER(P) \
         /*lint -save -e527 -e530 */ \
    { \
        (P) = (P); \
    } \
         /*lint -restore */
 #define DBG_UNREFERENCED_LOCAL_VARIABLE(V) \
         /*lint -save -e527 -e530 */ \
    { \
        (V) = (V); \
    } \
         /*lint -restore */

As a work-around if you do not choose to edit winnt.h, is to use the -emacro option as follows.

  -emacro(527,UNREFERENCED_PARAMETER,
   ,DBG_UNREFERENCED_PARAMETER,
   ,DBG_UNREFERENCED_LOCAL_VARIABLE)
  -emacro(530,UNREFERENCED_PARAMETER,
   ,DBG_UNREFERENCED_PARAMETER,
   ,DBG_UNREFERENCED_LOCAL_VARIABLE)

These have the effect of placing an additional wrapper around the original macro but it does no harm.

This might also have been a slightly better way to implement the original suppression.