lclint-interest message 182

From davidv@hsa.com.au Tue Jan  6 21:11:19 1998
Sender: davidv@stimpy
To: evans@cs.virginia.edu (David Evans)
Cc: lclint-interest@larch.lcs.mit.edu
Subject: Re: annotation help
References: <9801062357.AA21164@larch.lcs.mit.edu>
X-Face: #1jPhTl4Z])\d):;KBYaC_+6'h"JFu>eQ:"AE2D`h7(7[dwPE`lK+*K.m)s0m
        O_qcZvZNj_a[nMN_HA>b_
Date: 07 Jan 1998 12:03:28 +1100
In-Reply-To: evans@cs.virginia.edu's message of Tue, 6 Jan 98 18:57:29 -0500
Lines: 22
X-Mailer: Gnus v5.3/Emacs 19.34

evans@cs.virginia.edu (David Evans) writes:

> When you redeclare something, lclint will use the later definition
> (after warning you about the redeclartion and inconsistencies).  So,
> after you added the declaration with the /*@null@*/ annotation, you
> shouldn't get messages where XtAddCallback is called with a possibly
> null XtPointer argument.  

David, thank you for this clarification.  From my study of the LCLint
User's Guide, I thought that lclint would always use the first
definition.  I can see now that I was misreading section 4.3.
However, I can't find where the Guide documents the
use-of-later-definition behaviour you mention.

Thanks

...dav
-- 
David A Vincent       JUNK E-MAIL NOT WELCOME
Working (not speaking) for      Hydrographic Sciences Australia Pty Ltd
HSA phone extension number 27    within HSA, web site 
GCS C++++$ US++$ P+$ E++$ W++ N+++ w--- M++ Y+ PGP+ t-- G e++ h--- b+++