Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 32142:6b443ffa2f8b
applied changes from 1d2a25ce8baec7e426910e310ed73db0a4961c31
through 341e86eb5b808e0eab3242d7be676f83eca02b08
Original commit message:
Oh yeah, we're trying not to update ChangeLog.win32. Changing our
release process to not verify the date in that file
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 20 Jun 2011 05:29:11 +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; }