Your message dated Sat, 21 May 2011 14:41:35 +0100 with message-id <[email protected]> and subject line Re: Bug#504092: perl: unable to printf long long numbers has caused the Debian Bug report #504092, regarding perl: unable to printf long long numbers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 504092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504092 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: perl Version: 5.10.0-16 Hello, on i386 I have no way to printf long long values: holbe@darkside:/home/holbe% perl -e 'printf("%i\n", 11171763644)' -1 holbe@darkside:/home/holbe% perl -e 'printf("%li\n", 11171763644)' -1 holbe@darkside:/home/holbe% perl -e 'printf("%lli\n", 11171763644)' -1 holbe@darkside:/home/holbe% perl -e 'printf("%u\n", 11171763644)' 4294967295 holbe@darkside:/home/holbe% perl -e 'printf("%lu\n", 11171763644)' 4294967295 holbe@darkside:/home/holbe% perl -e 'printf("%llu\n", 11171763644)' 4294967295 %i, %li, %u and %lu are expected to fail, but %lli and %llu aren't. This is most likely something to forward upstream. regards Mario -- The social dynamics of the net are a direct consequence of the fact that nobody has yet developed a Remote Strangulation Protocol. -- Larry Wall
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Version: 5.12.3-6 On Fri, Oct 31, 2008 at 03:51:41PM +0100, Mario 'BitKoenig' Holbe wrote: > On Fri, Oct 31, 2008 at 11:56:26AM +0100, Mario 'BitKoenig' Holbe wrote: > > on i386 I have no way to printf long long values: > ... > > This is most likely something to forward upstream. > > ...or it's not? First, I thought it has something to do with how perl > stores integers, but it seems not to be that general... > > holbe@darkside:/home/holbe% perl -e '$a=11171763644; print "$a\n"' > 11171763644 > holbe@darkside:/home/holbe% perl -e '$a=11171763644; $a=int($a); print "$a\n"' > 11171763644 > holbe@darkside:/home/holbe% perl -e '$a=11171763644; printf("%lli\n", $a)' > -1 > > Seems to be an isolated printf issue only... Seems to be fixed in in the 5.12 packages compiled with -Duse64bitint, so closing bug report accordingly. Thanks, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
