Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 20475:2a2cc0b57d8f
propagate from branch 'im.pidgin.pidgin' (head 5e94d4a46251e35e2b640180905fe364b82355e5)
to branch 'im.pidgin.cpw.khc.msnp14' (head 7e42b1cb607bb785ef1a7d9e724f7d3ad0189f08)
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Sun, 22 Jul 2007 18:17:41 +0000 |
parents | c6e563dfaa7a |
children | 48d09d62912e |
line wrap: on
line source
#define DBUS_API_SUBJECT_TO_CHANGE #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; }