From: David Kastrup <dak@gnu.org>
Subject: Re: Reading portions of large files
Date: 11 Jan 2003 11:42:12 +0100 [thread overview]
Message-ID: <x5d6n4eznf.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.169.1042278925.21513.help-gnu-emacs@gnu.org
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > From: David Kastrup <dak@gnu.org>
> > Newsgroups: gnu.emacs.help
> > Date: 10 Jan 2003 21:51:49 +0100
> >
> > BTW, would it be terribly complicated to extend the range of Lisp
> > integers to 31bit?
>
> It's not terribly hard, but IIRC the current consensus among the Emacs
> maintainers is that it's not important enough to do that because
> before long all machines will have 64-bit compilers.
>
> Perhaps this should be discussed again on the developers' list.
>
> > Integers don't need any garbage collection or tag bits per se.
>
> They need to be distinguishable from other Lisp types, so their tag
> bitfield cannot have an arbitrary bit pattern.
Yes, but a single bit is sufficient for that distinction. This could
even speed up operations, since the sign bit is a candidate that can
be rather quickly checked.
Something like
if (x < 0)
will establish that something is an integer,
(x + 0x40000000)
will yield the value of the integer, and
(x | 0x8000000)
will convert an integer back to a Lisp number.
I don't know whether an integer Lisp object needs to be identical to
an integer. If it does, then the above needs an offset of 0x40000000
everywhere, of course.
> > Emacs has a most-positive-fixnum of 134217727, while XEmacs has
> > 1073741823, more than 8 times as much. So it would appear to be
> > possible in theory.
>
> IIRC, the XEmacs way requires extensive changes in how Emacs works,
> but I don't remember the details.
No clue about that.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-01-11 10:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.100.1042135372.21513.help-gnu-emacs@gnu.org>
2003-01-09 18:20 ` Reading portions of large files David Kastrup
2003-01-10 19:21 ` Eli Zaretskii
[not found] ` <mailman.153.1042230313.21513.help-gnu-emacs@gnu.org>
2003-01-10 20:51 ` David Kastrup
2003-01-11 8:51 ` Eli Zaretskii
[not found] ` <mailman.169.1042278925.21513.help-gnu-emacs@gnu.org>
2003-01-11 10:42 ` David Kastrup [this message]
2003-01-12 20:38 ` Stefan Monnier <foo@acm.com>
2003-01-13 7:40 ` Miles Bader
2003-01-13 7:42 ` Miles Bader
2003-01-13 7:55 ` David Kastrup
2003-01-13 8:05 ` Miles Bader
2003-01-20 7:50 ` Lee Sau Dan
2003-01-24 7:55 ` Mac
2003-01-27 14:44 ` Stefan Monnier <foo@acm.com>
2003-01-10 16:27 ` Eric Pement
2003-01-10 17:16 ` Brendan Halpin
2003-01-10 20:35 ` Benjamin Riefenstahl
2003-01-11 10:25 ` Klaus Berndl
2003-01-20 7:50 ` Lee Sau Dan
2003-01-20 12:46 ` Benjamin Riefenstahl
2003-01-20 7:50 ` Lee Sau Dan
2003-01-09 15:45 Gerald.Jean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5d6n4eznf.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.