Re: gEDA-user: Small patch to aid use of lib dmalloc

[timecop <timecop@xxxxxxxxx>]

> 5. retain the MYFREE() macro as its pointer clearing side effect is required
> 8. Instead of simply retaining MYFREE(p) (point 5), we could replace
> each use of it with an explicit:
>  free(p);
>  p = NULL;

Is this "MY" prefix actually in the code?
Most sane places call the kind of free your'e talking about here call
this macro SAFE_FREE() or SAFE_RELEASE() or something. it does
something along the lines of

if (arg) { free(arg); arg = null; }


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user