summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon McVittie <simon.mcvittie@collabora.co.uk>2010-09-22 16:24:21 (GMT)
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2010-09-22 16:24:21 (GMT)
commit8bbbdc94b4ba73ca11cb0c2e281e43dd8f955dd0 (patch)
tree918a960d27e9a6f7830770273c866de778730e13
parenta329baf55307d8dc65050494d5789fa8a7244135 (diff)
downloadtelepathy-haze-8bbbdc94b4ba73ca11cb0c2e281e43dd8f955dd0.tar.gz
telepathy-haze-8bbbdc94b4ba73ca11cb0c2e281e43dd8f955dd0.tar.xz
explain why a suspicious-looking use of purple_group_new is actually OK
-rw-r--r--src/contact-list.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/contact-list.c b/src/contact-list.c
index 92a9a0b..063c174 100644
--- a/src/contact-list.c
+++ b/src/contact-list.c
@@ -1076,6 +1076,8 @@ haze_contact_list_add_to_group (HazeContactList *self,
const gchar *bname =
haze_connection_handle_inspect (conn, TP_HANDLE_TYPE_CONTACT, handle);
PurpleBuddy *buddy;
+ /* This is correct, despite the naming: it returns a borrowed reference
+ * to an existing group (if possible) or to a new group (otherwise). */
PurpleGroup *group = purple_group_new (group_name);
g_return_if_fail (group != NULL);