Gnus development mailing list
 help / color / mirror / Atom feed
From: Aidan Kehoe <kehoea@parhasard.net>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: xemacs-patches@xemacs.org, bugs@gnus.org, ding@gnus.org
Subject: Re: [PATCH] Fix a bug with XEmacs and bignum support.
Date: Sun, 11 Jan 2009 15:55:45 +0000	[thread overview]
Message-ID: <18794.5761.657812.233052@parhasard.net> (raw)
In-Reply-To: <87sknpq37c.fsf@marauder.physik.uni-ulm.de>


 Ar an t-aonú lá déag de mí Eanair, scríobh Reiner Steib: 

 > On Sun, Jan 11 2009, Aidan Kehoe wrote:
 > 
 > > 2009-01-11  Aidan Kehoe  <kehoea@parhasard.net>
 > >
 > > 	* lisp/nnfolder.el (nnfolder-read-folder): 
 > > 	The (lsh -1 -1) trick to generate the greatest positive fixnum
 > > 	value doesn't work under an XEmacs with bignum support; use the
 > > 	most-positive-fixnum constant instead, available since GNU Emacs
 > > 	21.1 and XEmacs 21.1. 
 > 
 > 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))
 	      maxid start end newscantime
 	      novbuf articles newnum
 	      buffer-read-only)

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 on a 32-bit machine, and break the
algorithm.

-- 
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?

_______________________________________________
XEmacs-Patches mailing list
XEmacs-Patches@xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

  reply	other threads:[~2009-01-11 15:55 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 [this message]
2009-01-11 17:16     ` Reiner Steib
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=18794.5761.657812.233052@parhasard.net \
    --to=kehoea@parhasard.net \
    --cc=Reiner.Steib@gmx.de \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --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).