# HG changeset patch
# User Etan Reisner <pidgin@unreliablesource.net>
# Date 1231220199 0
# Node ID df6d3c3574ce914bee7e2767f7d34038bd2cd61c
# Parent  61f3a9f7a2200af0774de7f6a1e2e25466cdf02d
Make Purple::PluginPref->get_bounds be more perl-like.

It no longer expects to be called as:
	$ppref->get_bounds($min, $max)
or
	$ppref->get_bounds(\$min, \$max)
(I'm not even sure which one of those was intended to be correct, but
apparently they both crash.)

It now expects to be called like this:
	my ($min, $max) = $ppref->get_bounds();

diff -r 61f3a9f7a220 -r df6d3c3574ce ChangeLog.API
--- a/ChangeLog.API	Tue Jan 06 05:03:18 2009 +0000
+++ b/ChangeLog.API	Tue Jan 06 05:36:39 2009 +0000
@@ -1,5 +1,11 @@
 Pidgin and Finch: The Pimpin' Penguin IM Clients That're Good for the Soul
 
+version 2.5.4 (??/??/????):
+	perl:
+		Changed:
+		* Purple::PluginPref->get_bounds no longer takes two integer
+		  arguments it now returns two integers.
+
 version 2.5.3 (12/20/2008):
 	libpurple
 		Changed:
diff -r 61f3a9f7a220 -r df6d3c3574ce libpurple/plugins/perl/common/PluginPref.xs
--- a/libpurple/plugins/perl/common/PluginPref.xs	Tue Jan 06 05:03:18 2009 +0000
+++ b/libpurple/plugins/perl/common/PluginPref.xs	Tue Jan 06 05:36:39 2009 +0000
@@ -70,10 +70,16 @@
 
 
 void
-purple_plugin_pref_get_bounds(pref, min, max)
+purple_plugin_pref_get_bounds(pref, OUTLIST int min, OUTLIST int max)
 	Purple::PluginPref pref
-	int *min
-	int *max
+	# According to the perlxs manual page we shouldn't need to specify a
+	# prototype here because "[p]arameters preceded by OUTLIST keyword do
+	# not appear in the usage signature of the generated Perl function."
+	# however that appears to only work for the usage error message and
+	# not for the call to newXSproto. Since I can't find any documentation
+	# for newXSproto at the moment I have no idea if that matters so
+	# override the prototype here.
+	PROTOTYPE: $
 
 void
 purple_plugin_pref_get_choices(pref)