From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Emacs rewrite in a maintainable language Date: Mon, 12 Oct 2015 13:11:30 -0700 Organization: New Artisans LLC Message-ID: References: <561A19AB.5060001@cumego.com> <87io6dl0h0.fsf@wanadoo.es> <87lhb82qxc.fsf@gmail.com> <87oag4jk74.fsf@wanadoo.es> <87k2qrki45.fsf@wanadoo.es> <83mvvnooo4.fsf@gnu.org> <83lhb7oo4e.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444681231 31065 80.91.229.3 (12 Oct 2015 20:20:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 Oct 2015 20:20:31 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 12 22:20:31 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 1ZljaA-0004sV-CQ for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 22:20:30 +0200 Original-Received: from localhost ([::1]:58564 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zlja9-0005Nh-U3 for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 16:20:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZljRZ-0007vR-FL for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:11:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZljRW-00052d-M6 for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:11:37 -0400 Original-Received: from mail-pa0-x22f.google.com ([2607:f8b0:400e:c03::22f]:33149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZljRW-000524-Gn for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:11:34 -0400 Original-Received: by pabrc13 with SMTP id rc13so27260456pab.0 for ; Mon, 12 Oct 2015 13:11:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:subject:in-reply-to:date:organization:message-id :references:user-agent:mail-followup-to:mime-version:content-type; bh=HV+ZCY8t1uBLcBrNlxUctHR/qO43VZzCcxWO4M8S018=; b=pek/namIPbISAyNK/+X91NDLleAouVwNdaCiuvTFT4cmr3xCgdukr5qZcvARkWExGc Mea3x0Mbs6KPBEyMZxiAnZT/TFIcPuEjMHJ+sOZl3tzQ4W0SKGJCYPsdPkm+3fIjJR/q x8gWGsUyjx5AzhgRr4KJ06shaQZL/BTnZKAmO+0XzJXHECPy0VhgZ4oDtmpQYJQbD0pk eg6UWLkUmSu3r7LT/6gnMrkuYPTy46TnIYLmZx3TDG3JB0l5t/k0mU8StoDWMxDQyDUu qnuAFbY3B7nMV7OPE8hADTeIQ6lwFHlqAcZMpZXef6TTWDMnxavvytuSy0wHxff7YEY0 4QLA== X-Received: by 10.68.68.233 with SMTP id z9mr36347192pbt.132.1444680693768; Mon, 12 Oct 2015 13:11:33 -0700 (PDT) Original-Received: from Vulcan.local (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id ze3sm20047708pac.5.2015.10.12.13.11.33 for (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 12 Oct 2015 13:11:33 -0700 (PDT) Original-Received: by Vulcan.local (Postfix, from userid 501) id 60A33F2C090B; Mon, 12 Oct 2015 13:11:32 -0700 (PDT) In-Reply-To: <83lhb7oo4e.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Oct 2015 22:58:25 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22f 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:191396 Archived-At: >>>>> Eli Zaretskii writes: > On second thought, I don't think I understand the idea at all. What does it > mean "a Lispy language, easy to learn"? Is it a Lisp dialect, or is it C > with a set of Lisp-like macros preprocessed into C? What exactly are the C > aspects that we are trying to save the programmer from? And which part(s) of > the core do we expect to be able to rewrite in this "Lispy" language? Picture what we currently write in C, but a Lisp syntax, and all the macros we currently use removed. So, the essence of our C, written like it was Lisp. If that Lisp can get close enough to Emacs Lisp, so that knowing one means knowing the other, we've just made it easier for anyone to write what we now have to write in C. I can imagine that complex things, like type declarations, would be done with anti-quoted blocks, or by direct support for inclusion of header files. John