From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: LanX Newsgroups: gmane.emacs.help Subject: Re: About Emacs Modernisation Project Date: Tue, 1 Jun 2010 04:19:47 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <143c6d28-4423-4e43-9fc5-c0fb3340043b@c11g2000vbe.googlegroups.com> <0e994fe3-6dde-449f-879d-6701c7a195a9@e28g2000vbd.googlegroups.com> <8639x7x3jj.fsf@gmail.com> <87iq63wsvt.fsf@kuiper.lan.informatimago.com> <49573280-66a9-40a8-b556-be598a559cdc@l6g2000vbo.googlegroups.com> <87pr0buopy.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1291825070 8841 80.91.229.12 (8 Dec 2010 16:17:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2010 16:17:50 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 08 17:17:46 2010 Return-path: Envelope-to: geh-help-gnu-emacs@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 1PQMi3-0000Cc-Kk for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 17:17:39 +0100 Original-Received: from localhost ([127.0.0.1]:41060 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQMi2-0007cu-PF for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 11:17:38 -0500 Original-Path: usenet.stanford.edu!postnews.google.com!d12g2000vbr.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 22 Original-NNTP-Posting-Host: 188.97.6.227 Original-X-Trace: posting.google.com 1275391187 8697 127.0.0.1 (1 Jun 2010 11:19:47 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 1 Jun 2010 11:19:47 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: d12g2000vbr.googlegroups.com; posting-host=188.97.6.227; posting-account=W9fpQwoAAADZYmkl-8sXk1VPxG3rq-Pd User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.19) Gecko/2010040118 Ubuntu/8.10 (intrepid) Firefox/3.0.19,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:178519 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:75594 Archived-At: Hi > Do you realize that lisp is actually a very small core language? > (eval fits on a single page). I think that I made quite clear that I want this c/js/perl-style representation (lets call it PSILe) to be transformed to eLISP _before_ compilation. Macros will still work on the plain eLISP representation. (of course defining macros for PLISe wouldn't be easy feasible, but normal users won't miss macros...) The tricky part would be to find a representation that works without ambiguities in both directions, such that old lisp code could be used as a base for this "new" coding. I don't know if it's really feasible but it's for sure an interesting task. PLISe <-> eLISP -> Macro expansion -> compilation -> execution