view libpurple/purple-client-example.c @ 23582:a270bd4b5298

Just a few little cleanups. * I think we try to pair g_strdup() with g_free(). I don't know if it actually matters, but theoretically it could. * Changed this to use g_slist_prepend() when adding stuff to the queue. * Changed purple_requesticqstatusnote() to check if the linked list is empty and return TRUE as soon as the list becomes empty rather than on the next call to that function. * Don't remove and re-add the timer if it's already set. Unless there was a reason for that?
author Mark Doliner <mark@kingant.net>
date Mon, 21 Jul 2008 07:46:23 +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;
}