Mercurial > pidgin
view libpurple/purple-client-example.c @ 23700:187b0e2ff49d
Rely on xmlnode_insert_data to call strlen on a bunch of MSN status strings.
This has the side-effect of not triggering g_return_if_fail(length != 0) in
xmlnode_insert_data when you update your buddy icon and don't have a status
message, in which case msn_build_psm used to call insert_data("", 0). Perhaps
xmlnode_insert_data should short-circuit without logging an error if length ==
0?
author | Will Thompson <will.thompson@collabora.co.uk> |
---|---|
date | Mon, 11 Aug 2008 11:58:12 +0000 |
parents | 48d09d62912e |
children |
line wrap: on
line source
#ifndef DBUS_API_SUBJECT_TO_CHANGE #define DBUS_API_SUBJECT_TO_CHANGE #endif #include <stdio.h> #include <stdlib.h> #include "purple-client.h" /* This example demonstrates how to use libpurple-client to communicate with purple. The names and signatures of functions provided by libpurple-client are the same as those in purple. However, all structures (such as PurpleAccount) are opaque, that is, you can only use pointer to them. In fact, these pointers DO NOT actually point to anything, they are just integer identifiers of assigned to these structures by purple. So NEVER try to dereference these pointers. Integer ids as disguised as pointers to provide type checking and prevent mistakes such as passing an id of PurpleAccount when an id of PurpleBuddy is expected. According to glib manual, this technique is portable. */ int main (int argc, char **argv) { GList *alist, *node; purple_init(); alist = purple_accounts_get_all(); for (node = alist; node != NULL; node = node->next) { PurpleAccount *account = (PurpleAccount*) node->data; char *name = purple_account_get_username(account); g_print("Name: %s\n", name); g_free(name); } g_list_free(alist); return 0; }