From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: Guile in Emacs Date: Wed, 14 Apr 2010 16:10:55 +0200 Message-ID: References: <4B8147A9.7030504@gmail.com> <87wrxrr4md.fsf@gnu.org> <3vsk8ecg6a.fsf@fencepost.gnu.org> <873a0euot4.fsf@stupidchicken.com> <873a0cyv3r.fsf@lola.goethe.zz> <87aauiho3y.fsf_-_@lifelogs.com> <1271028837.6164.55.camel@dell-desktop.example.com> <1271102739.6067.38.camel@dell-desktop.example.com> <8039yz34ka.fsf@tiny.isode.net> <1271173887.6067.53.camel@dell-desktop.example.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1271254488 3481 80.91.229.12 (14 Apr 2010 14:14:48 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 14 Apr 2010 14:14:48 +0000 (UTC) Cc: Bruce Stephens , Thomas Lord , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 14 16:14:46 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 1O23Mb-0006rx-Rh for ged-emacs-devel@m.gmane.org; Wed, 14 Apr 2010 16:14:46 +0200 Original-Received: from localhost ([127.0.0.1]:53995 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O23Mb-00053E-4P for ged-emacs-devel@m.gmane.org; Wed, 14 Apr 2010 10:14:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O23JF-00049J-Gz for emacs-devel@gnu.org; Wed, 14 Apr 2010 10:11:17 -0400 Original-Received: from [140.186.70.92] (port=36748 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O23JC-00048G-Jy for emacs-devel@gnu.org; Wed, 14 Apr 2010 10:11:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O23J7-0002sO-24 for emacs-devel@gnu.org; Wed, 14 Apr 2010 10:11:14 -0400 Original-Received: from iwfs.imcode.com ([82.115.149.64]:49415 helo=gate.verona.se) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O23J6-0002qu-KA for emacs-devel@gnu.org; Wed, 14 Apr 2010 10:11:09 -0400 Original-Received: from localhost.localdomain (IDENT:1005@localhost [127.0.0.1]) by gate.verona.se (8.13.4/8.11.4) with ESMTP id o3EEAtl4015079; Wed, 14 Apr 2010 16:10:56 +0200 In-Reply-To: (Stefan Monnier's message of "Tue, 13 Apr 2010 12:07:18 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4-2.6 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:123638 Archived-At: Stefan Monnier writes: >> I dunno. Maybe. I'd guess that, no, that's not a >> good strategy. Four reasons come quickly to mind: > > I agree with your conclusion but for a very different reason. > In my opinion the actual language used is not very important because > most of the code that will be used with Emacs will be written > specifically for Emacs. > The availability of alternative implementations is also of no use > because changing the underlying implementation is the part that's > difficult (at least with Emacs's current structure). > > What matters is that we reuse some existing implementation and benefit > from all the work done on it, so we don't have to spend time working on > the Elisp byte-compiler. > > I like the idea of Guile not because it's using a "standard preexisting > language with libraries and experienced coders", but because it'll give > us a bunch of hackers working on efficient implementation, > multithreading, ... > > > Stefan > > > PS: The same holds for the redisplay engine; I really hope/wish we will > be able to switch to some other project's redisplay engine at some point. > IMHO it would be interesting to have Emacs as a set of components which could be plugged together, which also happened to include an elisp interpreter. This could work sort of like JNI in Java, or some other component model(Like one of the lightweight corba implementations) A start would be a plug-in model that allowed C plugins to be jacked into Emacs. That could allow other runtimes, like Guile, to run in Emacs and affect the Emacs internal state. -- Joakim Verona