I guess it's better than nothing but that won't work if x is some temporary local variable instead of the long term storage location. It also won't help much if

I guess it's better than nothing but that won't work if x is some temporary local variable instead of the long term storage location. It also won't help much if there are several pointers to the resource. As such I wonder if a macro is better that just explicitly nulling the pointer after free, at least there's no obfuscation of what's going on. Generally I agree with you though, setting pointers to NULL after free is good practice and probably worth enforcing in the coding style.