annotate src/eventloop.c @ 11719:109ee3bfeac5

[gaim-migrate @ 14010] SF Patch #1333770 from corfe83 "Many times in gaim we use the function g_slist_remove(list,node->data) to remove an element from a GSList. If we already have the pointer to the node we want to delete, it is faster to send it the pointer to the node to delete rather than the data of the node (we can do this by calling g_slist_delete_link(list,node)). This change was made while looking at glib's documentation and the code in glib's gslist.c. This is because as the remove/delete function traverses each node in the list, it doesn't need to spend an extra memory access to retrieve the data for each element in the node it is traversing and then compare, it can simply compare the pointer. In my tests outside of gaim, this makes a big difference if the node you are deleting is at a high index in the list. However, even if you're deleting the first node, it about breaks even. So, I've found each case in gaim where we are calling g_slist_remove, and we already have the pointer to the appropriate node to delete (this is often the case when we're doing a for or while loop on a GSList). I've then replaced it with the appropriate call to g_slist_delete_link. I, however, didn't do this in situations where we are explicitly removing the first element in the list, because in those situations it is an unnecessary change. There should be no difference in behavior, but just in case I've tried running it with valgrind, which reports the same number of memory leaks after my patch as before my patch. Of course, I can't guarantee that my normal behavior on gaim is hitting all the functions I've changed, but in general testing it Works For Me (tm)." As with the last patch, this one may not have a practical performance impact (or maybe it does, I have no idea), but it's not worse for any case. Given two ways of doing things where one is always at least as fast and may be faster under some cases, I like to prefer that faster way. This doesn't make the code any uglier, so I'm applying. committer: Tailor Script <[e-mail]>

/**
 * @file eventloop.c Gaim Event Loop API
 * @ingroup core
 *
 * gaim
 *
 * Gaim is the legal property of its developers, whose names are too numerous
 * to list here.  Please refer to the COPYRIGHT file distributed with this
 * source distribution.
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation; either version 2 of the License, or
 * (at your option) any later version.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with this program; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
#include "eventloop.h"

static GaimEventLoopUiOps *eventloop_ui_ops = NULL;

guint
gaim_timeout_add(guint interval, GSourceFunc function, gpointer data)
{
	GaimEventLoopUiOps *ops = gaim_eventloop_get_ui_ops();

	return ops->timeout_add(interval, function, data);
}

guint
gaim_timeout_remove(guint tag)
{
	GaimEventLoopUiOps *ops = gaim_eventloop_get_ui_ops();

	return ops->timeout_remove(tag);
}

guint
gaim_input_add(int source, GaimInputCondition condition, GaimInputFunction func, gpointer user_data)
{
	GaimEventLoopUiOps *ops = gaim_eventloop_get_ui_ops();

	return ops->input_add(source, condition, func, user_data);
}

guint
gaim_input_remove(guint tag)
{
	GaimEventLoopUiOps *ops = gaim_eventloop_get_ui_ops();

	return ops->input_remove(tag);
}

void
gaim_eventloop_set_ui_ops(GaimEventLoopUiOps *ops)
{
	eventloop_ui_ops = ops;
}

GaimEventLoopUiOps *
gaim_eventloop_get_ui_ops(void)
{
	g_return_val_if_fail(eventloop_ui_ops != NULL, NULL);

	return eventloop_ui_ops;
}