Subject: RE: strlen on a NULL
From: [email-masked] (Steve Greenland)

14 May 1998 02:01:35 -0700
Message-ID: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain
To: [email-masked]

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Wednesday, May 13, 1998 1:14 AM
>
> By the way, in 'free' it's getting worse,
> because you must also check not for pointing to a 'Zero', 
> this causes a crash. 

I'm not sure exactly what you mean by this phrase, but 
free(NULL) *is* defined: it's a no-op. If your implementation
crashes or otherwise misbehaves when you make the call "free(NULL)"
(or an equivalent), then the implementation is broken (assuming it
claims to be ISO C compliant, of course). 

Note that the sequence 

char *a = malloc(5);
free(a);
free(a);

*is* undefined; <a> is NOT set to NULL by the first call to free (how
could
it be?) but it does make the value of a invalid; the second call to free
attempts to free an invalid pointer...

Steve
-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".