From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Aidan Kehoe <kehoea@parhasard.net>
Cc: xemacs-patches@xemacs.org, ding@gnus.org
Subject: Re: [PATCH] Fix a bug with XEmacs and bignum support.
Date: Sun, 11 Jan 2009 18:16:07 +0100 [thread overview]
Message-ID: <878wphpxuw.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <18794.5761.657812.233052@parhasard.net> (Aidan Kehoe's message of "Sun, 11 Jan 2009 15:55:45 +0000")
On Sun, Jan 11 2009, Aidan Kehoe wrote:
> Ar an t-aonú lá déag de mí Eanair, scríobh Reiner Steib:
> > most-positive-fixnum is only available in Emacs 21 when requiring CL.
>
> Oops, you’re right, it was included it in C just after the release. Thanks
> for checking.
>
> > But as CL is required (for ignore-errors), I think this change is
> > fine, so I have installed it.
>
> It’s not, though, it needs to be something like the following in that case,
> since CL is available at compile time and not necessarily at runtime:
>
> --- /tmp/aidan/nnfolder.el.orig 2009-01-11 15:50:39.000000000 +0000
> +++ /tmp/aidan/nnfolder.el 2009-01-11 15:50:16.000000000 +0000
> @@ -899,7 +899,9 @@
> (active (or (cadr (assoc group nnfolder-group-alist))
> (cons 1 0)))
> (scantime (assoc group nnfolder-scantime-alist))
> - (minid (lsh -1 -1))
> + (minid (or (and (boundp 'most-positive-fixnum)
> + most-positive-fixnum)
> + 134217727))
> An (eval-when-compile most-positive-fixnum) isn’t appropriate, because the
> compile-time constant could be from a 64-bit machine, which would silently
> overflow in the Lisp reader under GNU
s/GNU/Emacs/, please. :-)
> on a 32-bit machine, and break the algorithm.
If you need to make sure that the correct runtime value is used, I
don't understand why you hard-code 134217727? I would have
expected...
(minid (or (and (boundp 'most-positive-fixnum)
most-positive-fixnum)
(lsh -1 -1)))
What am I missing?
On a 64-bit machine, I get:
,----[ M-x ielm RET ]
| ELISP> (lsh -1 -1)
| 576460752303423487
| ELISP> (emacs-version)
| "GNU Emacs 21.3.1 (x86_64-suse-linux, X toolkit, Xaw3d scroll bars)\n of 2004-1\
| 0-05 on prokofjieff"
| ELISP> (when (require 'cl) most-positive-fixnum)
| 576460752303423487
`----
When I used this machine(s) some years ago, I always compiled Gnus,
AUCTeX, BBDB, emacs-w3m, etc on a 64-bit machine and ran the compiled
Lisp code on both, 64-bit and 32-bit machines
(/usr/local/share/emacs/site-lisp shared via NFS).
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2009-01-11 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18793.58572.280122.113699@parhasard.net>
2009-01-11 15:20 ` Reiner Steib
2009-01-11 15:55 ` Aidan Kehoe
2009-01-11 17:16 ` Reiner Steib [this message]
2009-01-11 21:57 ` Aidan Kehoe
2009-01-12 22:45 ` Katsumi Yamaoka
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=878wphpxuw.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=kehoea@parhasard.net \
--cc=xemacs-patches@xemacs.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).