Ticket #105 (NULL checks)

[Andy Lester]

On Dec 31, 2008, at 11:55 AM, chromatic wrote:

> If we use -Wnonnull (implied by -Wall), we'll get compile warnings  
> when we
> pass potentially null parameters to functions which require non-null
> parameters.  There may be optimization possibilities there, but I  
> believe the
> primary purpose was to get these warnings.


Yes, that's exactly why.  Most of the instrumentation of ARGIN()/ 
ARGOUT() etc is there so that the compiler can track nulls.  I also  
set it up so that splint can track it as well.

attribute_nonnull is crucial.

xoxo,
Andy


--
Andy Lester => andy at petdance.com => www.petdance.com => AIM:petdance