From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Pushing the `gnus-range-*' functions down into the C layer Date: Fri, 10 Sep 2010 09:18:40 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <8762yd4r7j.fsf@lifelogs.com> References: <8739ti68sz.fsf@lifelogs.com> <87pqwm1dsl.fsf@uwakimon.sk.tsukuba.ac.jp> <87iq2d4sd5.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1284128355 22134 80.91.229.12 (10 Sep 2010 14:19:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 10 Sep 2010 14:19:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 10 16:19:15 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ou4Rb-0005gS-Le for ged-emacs-devel@m.gmane.org; Fri, 10 Sep 2010 16:19:11 +0200 Original-Received: from localhost ([127.0.0.1]:47724 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ou4RZ-0001zX-Fw for ged-emacs-devel@m.gmane.org; Fri, 10 Sep 2010 10:19:09 -0400 Original-Received: from [140.186.70.92] (port=51885 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ou4RQ-0001zS-Ea for emacs-devel@gnu.org; Fri, 10 Sep 2010 10:19:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ou4RM-0004c8-5A for emacs-devel@gnu.org; Fri, 10 Sep 2010 10:19:00 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:49549) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ou4RL-0004c0-Um for emacs-devel@gnu.org; Fri, 10 Sep 2010 10:18:56 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ou4RH-0005aF-3N for emacs-devel@gnu.org; Fri, 10 Sep 2010 16:18:51 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Sep 2010 16:18:51 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Sep 2010 16:18:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:mv2h+7b4sIKkUSyoRwYZ8tHm0A4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:129906 Archived-At: On Fri, 10 Sep 2010 16:01:41 +0200 Lars Magne Ingebrigtsen wrote: LMI> Ted Zlatanov writes: >> 64-bit int support in Emacs should not require a 64-bit system. If they >> are natively available it's faster, that's all. It's not like you'd be >> packing and unpacking the bits directly. LMI> Yeah. Bignum support in Emacs would totally rock. No more manual LMI> conversions to floating point numbers to do safe-ish computations on LMI> numbers that might be too big would be needed. LMI> But I suspect that it's a kinda big project. :-) If everything was inside a num64-* namespace and a num64.el package, it's a pretty easy implementation. I'm not an expert on numeric algorithms[1] but I'd guess the internals can be pretty easily implemented in ELisp as a list of up to 3 native 28-bit ints. In fact I'm surprised that doesn't exist yet; maybe I've missed it. Of course everyone will want 64-bit numbers native from the very start. I say that would delay the availability of the feature; just make people do (featurep 'num64) and get it done ASAP. Specifically for Gnus purposes, if range-* knew about the num64 API, it would be sufficient in order to use it. Ted [1] but I know enough not to assume anything at that level is trivial