From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Compilation to native Date: 07 Apr 2004 14:45:02 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <87eks0654s.fsf@sno.mundell.ukfsn.org> <87n06bp4ng.fsf@sno.mundell.ukfsn.org> <8765cwkejr.fsf@mail.jurta.org> <200404071157.UAA25094@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1081342353 11087 80.91.224.253 (7 Apr 2004 12:52:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 7 Apr 2004 12:52:33 +0000 (UTC) Cc: juri@jurta.org, matt@mundell.ukfsn.org, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Apr 07 14:52:07 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BBCXG-00064D-00 for ; Wed, 07 Apr 2004 14:52:06 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BBCXG-0003Fe-00 for ; Wed, 07 Apr 2004 14:52:06 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BBCWd-0000wa-Ih for emacs-devel@quimby.gnus.org; Wed, 07 Apr 2004 08:51:27 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BBCWA-0000vf-9v for emacs-devel@gnu.org; Wed, 07 Apr 2004 08:50:58 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BBCVY-0000lX-Ig for emacs-devel@gnu.org; Wed, 07 Apr 2004 08:50:51 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BBCQZ-0007td-Fm for emacs-devel@gnu.org; Wed, 07 Apr 2004 08:45:11 -0400 Original-Received: from fencepost.gnu.org ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.24) id 1BBCQL-0002u6-Li; Wed, 07 Apr 2004 08:44:58 -0400 Original-To: Kenichi Handa In-Reply-To: <200404071157.UAA25094@etlken.m17n.org> Original-Lines: 44 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21311 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21311 Kenichi Handa writes: > In article , Richard Stallman writes: > > > I thought about a different approach: predefined CCL programs > > could be statically converted into C code and compiled by a C > > compiler into Emacs core. > > > It is worth a try. On the other hand, I have to wonder > > if the CCL interpreter could be faster. > > I think there's not much room of improvement in the CCL > interpreter (i.e. the function ccl_driver). > > In addtion, in emacs-unicode, CCL is, by default, used only > for Ethiopic font encoding, and it can easily be changed not > to use CCL. > > So, I think it's not that worth working on CCL interpreter. If we have a development plan to switch to emacs-unicode soon. We really need to get a grip about what should be in the next feature release. If the unicode and bidi branches are considerable usable, what are we waiting for? We are in the situation that currently for many purposes one has to tell people "try using CVS". People get more and more to rely on it for daily work. This situation is unhealthy. If things like emacs-unicode and emacs-bidi are expected to cause longer-lasting trouble, then we should crank out something like a full-featured 21.5 or so just before merging them. If the merge phase leads to longer problems, we at least have a somewhat stable release to refer people to while we are sorting the problems out. If, on the other hand, users and developers of the unicode and bidi branches are confident enough that under _normal_ use (i.e., if one does not use bidi texts) stability should not be affected much, then I'd say "what the heck, give it to us". Maintaining separate branches for longer always leads to merging headaches. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum