effect of free()

Merlin Wilkerson merlin at mic.UUCP
Mon Sep 11 03:06:46 AEST 1989


In article <11018 at smoke.BRL.MIL> gwyn at brl.arpa (Doug Gwyn) writes:
>In article <29110 at news.Think.COM> barmar at think.COM (Barry Margolin) writes:
>>What may be needed to satisfy everyone is a built-in operation that
>>tells whether a pointer is valid to use.
>
>My opinion is that if the programmer doesn't know that without applying
>such a test, his code is out of control.
>
I agree.  I have sort of followed this conversation.  I can't think
of any reason why you would test to see if you had freed allocated 
space.  If need for the space was in fact conditional, I would still
want to get (and free) it explicitly.

built-in operations == built-in bullshit.

--------
merlin



More information about the Comp.lang.c mailing list