Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 20101:3a5f152e7ed0
This fixes compilation issues where old glib and either an old gcc or a
non-gcc compiler is used. I have opted to put the same preprocessor
directives in each plugin over including additional headers to fix this for
the purposes of staying as close as possible to the version I have in the
how-to documentss on the wiki. Fixes #3142 and bugs reported via the mailing
list, IRC channel, and XMPP conference.
author | John Bailey <rekkanoryo@rekkanoryo.org> |
---|---|
date | Mon, 17 Sep 2007 04:50:24 +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; }