GNU bug report logs - #30408
24.5; (format "%x" large-number) produces incorrect results

Previous Next

Full log

Message #51 received at 30408-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30408-done <at> debbugs.gnu.org, David Sitsky <david.sitsky <at> gmail.com>
Subject: Re: Checking for loss of information on integer conversion
Date: Thu, 29 Mar 2018 11:09:45 -0700

[Message part 1 (text/plain, inline)]

On 03/29/2018 04:11 AM, Eli Zaretskii wrote:
> I'd suggest, for a good measure, to have a variable which would force
> the conversion to floats, avoiding an error even without the trailing
> period.  We can later remove that variable, or make it a no-op, if the
> danger of breaking existing code turns out low or non-existent.

OK, I did that, by installing the attached into master, after installing 
the proposed patch.

As a result, unless the user sets the new variable 
read-integer-overflow-as-float, the Lisp reader now rejects the program 
(format "%x" 2738188573457603759) by signaling an overflow error. As 
this was the basis of the original bug report, I'm marking the bug as done.

[0001-New-experimental-variable-read-integer-overflow-as-f.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.