diff options
author | Ryan Lortie <desrt@desrt.ca> | 2014-10-17 14:38:43 +0200 |
---|---|---|
committer | Ryan Lortie <desrt@desrt.ca> | 2014-10-17 14:39:09 +0200 |
commit | e9b7c702404929c415320545905dcf008c9cd666 (patch) | |
tree | d79ed3e107c9503b639dfefc2a155616cecba8ae | |
parent | 18745ff674896c931379d097b18d74678044668e (diff) | |
download | glib-e9b7c702404929c415320545905dcf008c9cd666.tar.gz |
GHashTable: small docs fix
We use g_hash_table_unref() here, not g_object_unref().
-rw-r--r-- | glib/ghash.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/glib/ghash.c b/glib/ghash.c index 705880848..b42dd1423 100644 --- a/glib/ghash.c +++ b/glib/ghash.c @@ -369,7 +369,7 @@ g_hash_table_lookup_node (GHashTable *hash_table, * from a destroy notifier. The alternative would be to crash any second * (as keys, etc. will be NULL). * Applications need to either use g_hash_table_destroy, or ensure the hash - * table is empty prior to removing the last reference using g_object_unref. */ + * table is empty prior to removing the last reference using g_hash_table_unref(). */ g_assert (hash_table->ref_count > 0); hash_value = hash_table->hash_func (key); @@ -696,7 +696,7 @@ g_hash_table_new (GHashFunc hash_func, * permissible if the application still holds a reference to the hash table. * This means that you may need to ensure that the hash table is empty by * calling g_hash_table_remove_all before releasing the last reference using - * g_object_unref. + * g_hash_table_unref(). * * Returns: a new #GHashTable */ |