Ticket #105 (NULL checks)

[chromatic]

On Wednesday 31 December 2008 08:03:31 Mark Glines wrote:

> Ok, I've gone and read through RT #49316 and RT #50684.  It sounds an
> awful lot like attribute_nonnull is an optimization, not a constraint as
> I had originally thought.

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.

-- c