Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 25218:62c58a297fd2
propagate from branch 'im.pidgin.pidgin' (head 7561443e7b6e50cd96cac03b88cbb8fab1f45d84)
to branch 'im.pidgin.cpw.malu.xmpp.ibb_ft' (head cd5d15e9034056e52d54827d65c4f32f57430136)
author | Marcus Lundblad <ml@update.uu.se> |
---|---|
date | Sun, 28 Sep 2008 11:08:21 +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; }