From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel Subject: Re: GSoC: Emacs Lisp support for GNU Guile Date: Tue, 31 Mar 2009 23:34:48 +0100 Message-ID: <87r60dnwxj.fsf@arudy.ossau.uklinux.net> References: <87skktqvwg.fsf@unknownlamer.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1238538917 14777 80.91.229.12 (31 Mar 2009 22:35:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 31 Mar 2009 22:35:17 +0000 (UTC) Cc: Daniel Kraft , guile-devel@gnu.org To: Clinton Ebadi Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Apr 01 00:36:33 2009 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LomZF-0001ny-5D for guile-devel@m.gmane.org; Wed, 01 Apr 2009 00:36:25 +0200 Original-Received: from localhost ([127.0.0.1]:36489 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LomXr-0002Sx-AH for guile-devel@m.gmane.org; Tue, 31 Mar 2009 18:34:59 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LomXn-0002Sc-J3 for guile-devel@gnu.org; Tue, 31 Mar 2009 18:34:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LomXi-0002Ob-Mo for guile-devel@gnu.org; Tue, 31 Mar 2009 18:34:54 -0400 Original-Received: from [199.232.76.173] (port=51677 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LomXi-0002OV-Jz for guile-devel@gnu.org; Tue, 31 Mar 2009 18:34:50 -0400 Original-Received: from mail3.uklinux.net ([80.84.72.33]:44436) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LomXi-0008Kk-53 for guile-devel@gnu.org; Tue, 31 Mar 2009 18:34:50 -0400 Original-Received: from arudy (host86-157-180-39.range86-157.btcentralplus.com [86.157.180.39]) by mail3.uklinux.net (Postfix) with ESMTP id 97C781F6A3B; Tue, 31 Mar 2009 23:34:49 +0100 (BST) Original-Received: from arudy.ossau.uklinux.net (arudy [127.0.0.1]) by arudy (Postfix) with ESMTP id 05BCC38013; Tue, 31 Mar 2009 23:34:48 +0100 (BST) In-Reply-To: <87skktqvwg.fsf@unknownlamer.org> (Clinton Ebadi's message of "Tue\, 31 Mar 2009 16\:28\:47 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:8370 Archived-At: This email is going to be about Guile details that the Emacs crowd probably won't be interested in, so I've removed emacs-devel. Clinton Ebadi writes: > There is already a working elisp->scheme translator for the interpeter > in lang/elisp. I've poked about in it and it would be fairly > straightfoward to port it to the VM by retargetting it to GHIL and > replacing the @fop and @bind operators in the interpeter with a bit of > GHIL implementing the same behavior. > > As a general implemention order I suggest: > > - Replace @fop and @bind with a GHIL fragment implementing the same > behavior > - Integrate the elisp->scheme translator into the VM compiler framework > - Retarget the elisp translator from Scheme to GHIL Agreed with all that. Also I think there is still some support in Guile's reader code for Elisp stuff such as [...] vectors. That should probably be removed and replaced by a proper Elisp parser written in Scheme. > If there is time left (the above tasks should take maybe a month, > perhaps more) then a few more tasks would be useful as far as cleaning > up the implementation of Guile: > > - Remove handling of NIL in Scheme. This special casing is, in my > opinion, distressingly unclean. This would require adding a new > ELISP-IF form that accepts #f/nil as false values I'm not clear what you mean here. Can you expand on this? > - Reimplement the basic elisp list operators in elisp/ghil rather than > using the existing Scheme implementations Sounds right, but do you have a specific reason? > - [Potentially] Remove value/function slots from Guile's symbol type > and implement the Lisp-2ness of elisp in another way That sounds too dull for GSoC! More a matter of API continuity than of anything technically interesting. Or am I missing something? > - [Assuming the above is done; if not ((fref SYMBOL) ...) works > already] Implement a convenient way to call elisp functions from > Scheme. Something like (funcall SYMBOL ...) I thought that was already possible... yes, using elisp-function, use-elisp-file or use-elisp-library. Regards, Neil