view libpurple/purple-client-example.c @ 16997:34d9037a228c

RC4 support to libpurple's cipher.c. applied changes from 16cddf101af9bec7aa7546f67d791389bb82a8c5 through eb65d87cbe206ce460c3647f24e6cc06bb1e83fe Patch from Nathan Peterson to add RC4 support. applied changes from eb65d87cbe206ce460c3647f24e6cc06bb1e83fe through c27d5698b3cb75df5ec296031e29e46440ac2303 Add rc4_get_key_size.
author Jeffrey Connelly <jaconnel@calpoly.edu>
date Thu, 10 May 2007 02:58:35 +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;
}