Description: Mention "use bigint;" in POD under CAVEATS
Bug: https://rt.cpan.org/Public/Bug/Display.html?id=78653
Bug-Debian: http://bugs.debian.org/723021
Author: Axel Beckert <abe@debian.org>

Index: libstring-koremutake-perl/lib/String/Koremutake.pm
===================================================================
--- libstring-koremutake-perl.orig/lib/String/Koremutake.pm	2013-08-29 16:55:22.000000000 +0200
+++ libstring-koremutake-perl/lib/String/Koremutake.pm	2013-12-13 21:31:55.000000000 +0100
@@ -138,6 +138,48 @@
 
   my $i = $k->koremutake_to_integer('koremutake'); # 10610353957
 
+=head1 CAVEATS
+
+You need to "use bigint;" if you want String::Koremutake to work with
+integers larger than what fits into a normal Perl integer before it
+gets converted to a floating point number on your platform.
+
+=head2 Example
+
+Without "use bigint;" big integers get converted to fixed precision
+floating point numbers:
+
+  $ perl -MString::Koremutake -le '
+    my $a = 65536**4;
+    my $k = String::Koremutake->new;
+    foreach my $b ($a, $a+1, $a+2, $a+3) {
+      print "$b: ".$k->integer_to_koremutake($b);
+    }'
+  1.84467440737096e+19: bibababababababababa
+  1.84467440737096e+19: bibababababababababa
+  1.84467440737096e+19: bibababababababababa
+  1.84467440737096e+19: bibababababababababa
+
+If you use that large integers, you should add "use bigint;" to your
+program which solves that issue:
+
+  $ perl -Mbigint -MString::Koremutake -le '
+    my $a = 65536**4;
+    my $k = String::Koremutake->new;
+    foreach my $b ($a, $a+1, $a+2, $a+3) {
+      print "$b: ".$k->integer_to_koremutake($b);
+    }'
+  18446744073709551616: bibababababababababa
+  18446744073709551617: bibababababababababe
+  18446744073709551618: bibababababababababi
+  18446744073709551619: bibababababababababo
+
+It will likely save you from other issues with big integers, too.
+
+Note that "foreach my $b ($a .. $a+3)" doesn't work either as the ".."
+operator can't be overloaded. See CAVEATS in "perldoc bigint" for
+details.
+
 =head1 BUGS AND LIMITATIONS                                                     
                                                                                 
 No bugs have been reported.