From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Compilation to native Date: Wed, 7 Apr 2004 22:12:43 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200404071312.WAA25268@etlken.m17n.org> 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 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1081346184 21659 80.91.224.253 (7 Apr 2004 13:56:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 7 Apr 2004 13:56:24 +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 15:56:12 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 1BBDXI-0002zd-00 for ; Wed, 07 Apr 2004 15:56:12 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BBDXH-00047f-00 for ; Wed, 07 Apr 2004 15:56:12 +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 1BBDW2-0004yV-Te for emacs-devel@quimby.gnus.org; Wed, 07 Apr 2004 09:54:54 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BBDLt-0001Cq-Tx for emacs-devel@gnu.org; Wed, 07 Apr 2004 09:44:26 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BBDKd-0000hw-Qg for emacs-devel@gnu.org; Wed, 07 Apr 2004 09:43:39 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1BBDK1-0000Y7-HK; Wed, 07 Apr 2004 09:42:29 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by mx20.gnu.org with esmtp (Exim 4.30) id 1BBCrH-0004jn-Ep; Wed, 07 Apr 2004 09:12:47 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/8.11.6) with ESMTP id i37DCi803062; Wed, 7 Apr 2004 22:12:44 +0900 (JST) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.6p2/8.11.6) with ESMTP id i37DCh904046; Wed, 7 Apr 2004 22:12:43 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id WAA25268; Wed, 7 Apr 2004 22:12:43 +0900 (JST) Original-To: dak@gnu.org In-reply-to: (message from David Kastrup on 07 Apr 2004 14:45:02 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) 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:21313 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21313 In article , David Kastrup writes: > 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? I think Unicode branch is fairly usable in normal use. At least it's stable enough for my daily work. But if it is used with third party packages, I think some of them must be adjusted for emacs-unicode. Bidi branch is far from usable. I created that branch mainly for that the other people can contribute. It's very difficult to find a time to work on it for me. > 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. I fully agree. When I synchronized emacs-unicode branch to HEAD a half year ago, it took about 10 days concentrated work. I think it will need the same amount of work to merge emacs-unicode to HEAD. If Richard says "go ahead", I'll manage to make that time. --- Ken'ichi HANDA handa@m17n.org