comparison libpurple/plugins/joinpart.c @ 17703:0f4a562b38d1

libpurple should not use glib eventloop stuff directly, since we have our own eventloop abstraction. This leaves just one hack in blist.c.

17700:9187a19d72a7

	/* Destroy the hash table. The core plugin code will
	 * disconnect the signals, and since Purple is single-threaded,
	 * we don't have to worry one will be called after this. */
	g_hash_table_destroy((GHashTable *)data[0]);

	g_source_remove(GPOINTER_TO_UINT(data[1]));
	g_free(data);

	return TRUE;
}

17703:0f4a562b38d1

	/* Destroy the hash table. The core plugin code will
	 * disconnect the signals, and since Purple is single-threaded,
	 * we don't have to worry one will be called after this. */
	g_hash_table_destroy((GHashTable *)data[0]);

	purple_timeout_remove(GPOINTER_TO_UINT(data[1]));
	g_free(data);

	return TRUE;
}