diff options
author | Elliott Sales de Andrade <quantum.analyst@gmail.com> | 2023-03-21 00:39:45 -0500 |
---|---|---|
committer | Elliott Sales de Andrade <quantum.analyst@gmail.com> | 2023-03-21 00:39:45 -0500 |
commit | 1b4f76976e1a069831b98518588f587be79b122c (patch) | |
tree | 0558873858c1d4b3fb27069c4932d729e3a7f397 /libpurple/server.c | |
parent | ae674f38b973f59afa38f5fbcb8b4c069188e59f (diff) | |
download | pidgin-1b4f76976e1a069831b98518588f587be79b122c.tar.gz |
Use g_clear_* helpers where useful
That is:
* when the variable is set to `NULL` right after freeing
* when the variable is checked for non-`NULL` before freeing
* when the variable is a global (because they should be set to `NULL`, even if we don't really claim that things can be re-init'd)
Testing Done:
Compiled, and ran tests in valgrind.
Reviewed at https://reviews.imfreedom.org/r/2369/
Diffstat (limited to 'libpurple/server.c')
-rw-r--r-- | libpurple/server.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/libpurple/server.c b/libpurple/server.c index 61fe6ed031..8395049a4c 100644 --- a/libpurple/server.c +++ b/libpurple/server.c @@ -457,8 +457,7 @@ struct chat_invite_data { static void chat_invite_data_free(struct chat_invite_data *cid) { - if (cid->components) - g_hash_table_destroy(cid->components); + g_clear_pointer(&cid->components, g_hash_table_destroy); g_free(cid); } |