void safer_free(void **x) {
if(x!=NULL && *x!=NULL) {
free(*x);
}
*x = NULL;
}
the key part being to set the original pointer to NULL so a future use will cause an exception, not a vulnerability. void safer_free(void **x) {
if(x!=NULL && *x!=NULL) {
free(*x);
}
*x = NULL;
}
the key part being to set the original pointer to NULL so a future use will cause an exception, not a vulnerability.It works in the vast majority of cases. In the rare other cases, you should spend some extra thought on your pointer usage to make sure you have a set of abstractions that let a human reason about the memory sensibly (either that or an insane number of test cases to catch any problem). Someone else mentioned reference counting, and that can be a good idea.
The bottom line is you need to do something to make sure you're not doing use-after-free, and it's mostly not difficult.
Overall, it's not useless, but it's really not worth modifying the language for it.
There is probably scope for use of C11 _Generic, but I don't think you could support user-defined types in that way.
The usual macro problems apply when trying to do it as a macro:
#define FREE(X) (free(X),(X)=NULL,(void)0)
In C++ you can do something like this, which works well enough: (I don't use this specifically myself, but I have something similar for COM objects) template<class T>
static void Free(T *&p) {
free(p);
p=nullptr;
}
This isn't completely useless, but it's not worth sweating blood over. Personally I think I've had more mileage from good-quality debug functionality in the memory allocator: fill newly-allocated and newly-freed regions with junk; check junk and metadata periodically; unmap regions promptly; and so on.Or rather, more likely, they were so focused on efficiency (because that's what you do when you have a 1Mhz computer), that the idea of making things easier for people in this way didn't cross their mind.
Burroughs did not have this issue with ESPOL and NEWP almost 10 years earlier before C was born.
Nor did the UK Navy with Algol 68RS or the multiple institutes using PL/I variants.
Burroughs B5500 was created in 1961 and executed far slower and had less memory than a PDP-11, yet it was able to have a full OS written in ESPOL, an ALGOL dialect with intrisics for CPU instructions and explicit UNSAFE statements.
So if a 10 year old machine by the time C was created for computers with " extra overhead was unbearable." and " what you do when you have a 1Mhz computer" was already able to execute an Algol dialect with enough performance, what does that say of C in regards to language design?