Why are integers in Elisp restricted on some machines to 27 or 28 bits
of accuracy? Wouldn't it be better if integers could be a full 32
bits in size, by borrowing from the following C++ code and translating
it to C and Elisp.

#include
#define null (0)

template
class ptr
{
private:
X* inner_ptr;

public:
ptr()
{
inner_ptr = null;
}

Am 06.05.2008 um 10:00 schrieb Davin Pearson:

Because some bits (4) are used internally for Lisp purposes. In this
millenium it's so easy to migrate to a useful processor with 64 or
more bits and an operating system that supports these wealth that I
don't see much sense in complaining.

--
Greetings

Pete

The light at the end of the tunnel has been turned off due to budget
cuts.

Peter Dyballa writes:

It would be easily possible to use 31 bit integers and use 5 bits for
Lisp purposes (when the lowest bit is 1, we are talking about integers,
or a scheme like that).