Thanks. It would be good to document it (and that all the _new's
return NULL on an error).
On 7/30/2021 3:03 PM, Matt Caswell wrote:
All our _free functions will accept NULL. We rely on this extensively
*everywhere*. We perhaps could be better at documenting it, but you can rely on
it.
Matt
On 30/07/2021 17:55, Ken Goldman wrote:
It would be nice if the documentation would guarantee that
this function is a no-op when the parameter is NULL - like
the standard free() call.
This would save coding (if not NULL) all the time.
Same comment for all the _free functions.
I know I can look at the code, but that doesn't
provide an API guarantee.
