[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Checking for loss of information on integer conversion
From: |
Juliusz Chroboczek |
Subject: |
Re: Checking for loss of information on integer conversion |
Date: |
Mon, 19 Feb 2018 00:46:44 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
>>> Another possibility would be for Emacs to signal an error when
>>> reading any integer that does not fit in fixnum bounds.
>> Please do that.
> That would be a regression. On 32bit systems, there are various
> circumstances where we need to read a 32bit ID
I can see how this could be a problem, but I still find the current
semantics pretty horrible, and completely different from what any Lisp
hacker would expect.
Perhaps Emacs could acquire small bignums? Say, boxed 64-bit integers
with signal on overflow?
> On 64bit systems (and 32bit systems built with wide-ints),
> I don't see such a clear need to convert a large integer into a float,
> so on those systems I think it's OK to just signal an error.
Please.
> Stefan "still living in the 32bit world"
We like you nonetheless.
-- Juliusz
- Checking for loss of information on integer conversion, Paul Eggert, 2018/02/17
- Re: Checking for loss of information on integer conversion, Eli Zaretskii, 2018/02/18
- Re: Checking for loss of information on integer conversion, Juliusz Chroboczek, 2018/02/18
- Re: Checking for loss of information on integer conversion, Richard Stallman, 2018/02/19
- Re: Checking for loss of information on integer conversion, Juliusz Chroboczek, 2018/02/22
- Re: Checking for loss of information on integer conversion, Eli Zaretskii, 2018/02/22
- Re: Checking for loss of information on integer conversion, Stefan Monnier, 2018/02/22
- Re: Checking for loss of information on integer conversion, Richard Stallman, 2018/02/23
Re: Checking for loss of information on integer conversion, John Wiegley, 2018/02/19