comparison ChangeLog.API @ 25414:efde7e6ed5f2

There's no reason for these to not be const is there? This doesn't break API compatibility in my mind. Does anyone think it does?
author Mark Doliner <mark@kingant.net>
date Tue, 03 Feb 2009 18:56:17 +0000
parents ff883620d9d4
children 96814f0cfe49 af42303654a5
comparison
equal deleted inserted replaced
25413:cd7aa76faef6 25414:efde7e6ed5f2
4 libpurple: 4 libpurple:
5 Changed: 5 Changed:
6 * purple_status_type_new now defaults "saveable" to TRUE. 6 * purple_status_type_new now defaults "saveable" to TRUE.
7 This was necessary in order to maintain the current behavior 7 This was necessary in order to maintain the current behavior
8 while fixing non-saveable statuses not to be saved. 8 while fixing non-saveable statuses not to be saved.
9 * xmlnode_get_prefix, xmlnode_to_str and xmlnode_to_formatted_str
10 now all take a const xmlnode* instead of an xmlnode*
9 11
10 version 2.5.4 (01/12/2009): 12 version 2.5.4 (01/12/2009):
11 perl: 13 perl:
12 Changed: 14 Changed:
13 * Purple::PluginPref->get_bounds no longer takes two integer 15 * Purple::PluginPref->get_bounds no longer takes two integer