Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 28318:38f09799476a
Didn't realize I hadn't pushed this before the string freeze so we get to do
it here instead.
*** Plucked rev 6b146c92bd0f878c7321a914c74044d50273abcf (deryni@pidgin.im):
I noticed the other day that we don't have a \"Join a Chat\" menu item in the
Conversation menu. This fixes that.
author | Etan Reisner <pidgin@unreliablesource.net> |
---|---|
date | Wed, 22 Jul 2009 02:34:56 +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; }