Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 21736:4d776104ec0e
Somehow this message got changed to only say ICQ instead of AIM/ICQ in
revision 99cf698cfc5a930dda2b67b063730d528d92e976, when this bit of
code was moved from libaim.c and libicq.c back into oscar.c.
I also changed it to mention direct IM, as well, and the text now spans
three lines instead of just two, since there is plenty of room on the
advanced tab for oscar accounts, and I thought using three lines might
make it easier for translators
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 03 Dec 2007 05:31:36 +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; }