From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: immerrr again Newsgroups: gmane.emacs.devel Subject: Re: Emacs rewrite in a maintainable language Date: Tue, 13 Oct 2015 09:00:15 +0300 Message-ID: References: <561A19AB.5060001@cumego.com> <87io6dl0h0.fsf@wanadoo.es> <87lhb82qxc.fsf@gmail.com> <87oag4jk74.fsf@wanadoo.es> <87k2qrki45.fsf@wanadoo.es> <11a21a29-f4e7-4c75-9c63-b55f535d6a91@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1444716042 4197 80.91.229.3 (13 Oct 2015 06:00:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 13 Oct 2015 06:00:42 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 13 08:00:35 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZlsdX-0004Nv-7m for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 08:00:35 +0200 Original-Received: from localhost ([::1]:60768 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlsdW-0003ar-Lj for ged-emacs-devel@m.gmane.org; Tue, 13 Oct 2015 02:00:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42295) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlsdG-0003Wk-58 for emacs-devel@gnu.org; Tue, 13 Oct 2015 02:00:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZlsdE-0006zH-Rp for emacs-devel@gnu.org; Tue, 13 Oct 2015 02:00:18 -0400 Original-Received: from mail-yk0-x233.google.com ([2607:f8b0:4002:c07::233]:33347) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlsdE-0006z8-Nn for emacs-devel@gnu.org; Tue, 13 Oct 2015 02:00:16 -0400 Original-Received: by ykoo7 with SMTP id o7so7132818yko.0 for ; Mon, 12 Oct 2015 23:00:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bwF677qud0MSbV9npNtrvaMJ/P9viFtAhlF2Q4ZX5F4=; b=mesMDenwc+tpalgj2nt71Q4HlX0WvEeS2l5K+v3IfXZU9e55YAZpZ/7eWsGhQ0ykQo xklZiqluE5Si5Bxz48yygfLbJ7CAqLGxD2SY9Kyib3BqEtPtrmreewqc+9/oKmKFjaX6 xttgmAbL0oVLrVWdLcFGoYRXwmjk+cM3IwB7eRelsd3+Zc8lyjzltbaCdg13+8eJhuvw LqD7JxvAZ+fnOrhjJf9ziLhkpbaUzKg2SGnX5PnBrRm8hrhNIsvcNXnPgshQPDK3aZns 23YNsbpM/br0f95O+ebyqiWBjl3TJ+SZF+10A+rnJxv7rF2VFq6LUWoLyE7UxagaBRIG dXvA== X-Received: by 10.13.238.135 with SMTP id x129mr22751476ywe.245.1444716016242; Mon, 12 Oct 2015 23:00:16 -0700 (PDT) Original-Received: by 10.13.212.197 with HTTP; Mon, 12 Oct 2015 23:00:15 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4002:c07::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191429 Archived-At: On Tue, Oct 13, 2015 at 7:18 AM, John Wiegley wrote: > > If the gap between C (or a hypothetical Lisp-like), and Emacs Lisp, could be > reduced to zero, I'd absolutely want everything to be in Emacs Lisp. That has > been my dream for Emacs since I can remember, as I'm prefer playing on the > Lisp side much more than the C side. > > I once tried to make Emacs Lisp my "primary language". The speed just wasn't > there, not to mention a few other things (control over memory layout, direct > access to file handles, integration with C libraries, etc). There are several > things we'd need to turn Emacs Lisp into a general purpose, well-performing > language, sufficient to replace all our C code. > A wild idea would be to try rewriting the Emacs Lisp interpreter in RPython [1]. It is a "framework for writing dynamic language interpreters" and is used for implementing pypy [2] and pixie [3] (which is a Lisp dialect). It accepts interpreter code in a subset of Python, which is still quite high-level, that can be translated to C using GCC as a backend. It comes with interpreter-related goodies, like FFI, several implementations of GC, code flow analyzers and an implementation of a tracing JIT. I would guess it would help with performance a bit. 1. https://rpython.readthedocs.org/ 2. http://pypy.org/ 3. https://github.com/pixie-lang/pixie