From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Clojure-like syntactic sugar for an anonymous function literal Date: Thu, 22 Jan 2015 18:36:29 -0500 Message-ID: References: <54C15ECA.5050008@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1421969814 18954 80.91.229.3 (22 Jan 2015 23:36:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2015 23:36:54 +0000 (UTC) Cc: Oleh , emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 23 00:36:53 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 1YERIy-00047Y-AZ for ged-emacs-devel@m.gmane.org; Fri, 23 Jan 2015 00:36:52 +0100 Original-Received: from localhost ([::1]:56536 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YERIx-0006Qv-S2 for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2015 18:36:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YERIf-0006Kc-8r for emacs-devel@gnu.org; Thu, 22 Jan 2015 18:36:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YERIc-00053L-3O for emacs-devel@gnu.org; Thu, 22 Jan 2015 18:36:33 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:17258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YERIb-00053B-Vr for emacs-devel@gnu.org; Thu, 22 Jan 2015 18:36:30 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwPAOwQflSnWBWM/2dsb2JhbABbgweDYIVaxR0EAgKBJBcBAQEBAQF8hAMBAQMBViMFCwsOJhIUGA0kiEoJ1lkBAQEBBgEBAQEekBdYB4RIBYsBkjGPc4QChBkhgTSBQwEBAQ X-IPAS-Result: AjwPAOwQflSnWBWM/2dsb2JhbABbgweDYIVaxR0EAgKBJBcBAQEBAQF8hAMBAQMBViMFCwsOJhIUGA0kiEoJ1lkBAQEBBgEBAQEekBdYB4RIBYsBkjGPc4QChBkhgTSBQwEBAQ X-IronPort-AV: E=Sophos;i="5.07,502,1413259200"; d="scan'208";a="108511422" Original-Received: from 167-88-21-140.cpe.teksavvy.com (HELO pastel.home) ([167.88.21.140]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Jan 2015 18:36:29 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 32789EDE; Thu, 22 Jan 2015 18:36:29 -0500 (EST) In-Reply-To: <54C15ECA.5050008@dancol.org> (Daniel Colascione's message of "Thu, 22 Jan 2015 12:34:18 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:181640 Archived-At: > That's a problem with any lisp that provides a reader-macro facility. > The onus is on the authors of macro packages to create macros that work > well with the existing emacs-lisp-mode parser. That's a good point. >>> So I'm currently against addition of CL style reader macros. > Stefan, is emacs-lisp-mode support your only objection? Yes and no. No in the sense that I expect that introducing such reader macros will have consequences that go further than just "emacs-lisp-mode support". Maybe we could introduce a more limited form of reader macros. E.g. allow # and make the reader return (funcall (cdr (assq reader-macro-alist)) ) So it would allow introducing a special regexp syntax #r"regexp" (which would for example swap the meaning of ( and \( and things like that), but it wouldn't allow defining "raw string" (backslashes would quote the " just as usual). > We already have plenty of libraries defining "control flow" structures; > look at all the anaphoric-if libraries out there. Agreed, and I think it's a good thing. Stefan