Mercurial > pidgin
view libpurple/purple-client-example.c @ 29447:c203ceb5bd9a
propagate from branch 'im.pidgin.pidgin' (head 6729d3dea8df2203383212a82eddd4697ea70ee9)
to branch 'im.pidgin.cpw.rekkanoryo.icqxstatus' (head 0dd11b78b526e2c42337a6749d942bb0a93fe958)
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Tue, 25 Nov 2008 17:24:40 +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; }