From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Emacs rewrite in a maintainable language Date: Mon, 12 Oct 2015 22:46:13 +0200 Message-ID: <87fv1fke7e.fsf@wanadoo.es> 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 1444682810 23251 80.91.229.3 (12 Oct 2015 20:46:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 Oct 2015 20:46:50 +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:46:37 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 1ZljzQ-0005Wv-Pe for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 22:46:36 +0200 Original-Received: from localhost ([::1]:58720 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZljzQ-0004q6-4V for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 16:46:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZljzM-0004pv-Rk for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:46:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZljzJ-0007OE-CW for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:46:32 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:55296) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZljzJ-0007O3-69 for emacs-devel@gnu.org; Mon, 12 Oct 2015 16:46:29 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZljzE-0005Ld-BK for emacs-devel@gnu.org; Mon, 12 Oct 2015 22:46:24 +0200 Original-Received: from 198.red-83-32-113.dynamicip.rima-tde.net ([83.32.113.198]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Oct 2015 22:46:24 +0200 Original-Received: from ofv by 198.red-83-32-113.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Oct 2015 22:46:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 198.red-83-32-113.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:du0Wup0qvJIjLkyzy4MtOr/++IE= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:191400 Archived-At: John Wiegley writes: >>>>>> 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. Yes. > 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. The project I made for extending/replacing a C++ code base uses Clang for parsing the headers, extracting the interesting bits and emitting the information required by the Lispy language to access or call the C++ part. As depending on Clang is not allowed, another tool is required, but there are some, or the info can be generated once and put into a file and then maintained as the C source code changes, altough the problem with this approach are the platform-dependent bits.