unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Schmidt <christopher@ch.ristopher.com>
To: 11782@debbugs.gnu.org
Subject: bug#11782: 24.1; closure is not self-quoting
Date: Tue, 28 May 2013 23:35:08 +0100 (BST)	[thread overview]
Message-ID: <87obburavs@ch.ristopher.com> (raw)
In-Reply-To: <jwvobbuj0to.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 28 May 2013 16:40:44 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

Hi Stefan,

> Could you expand on why you think it's severe?

I think this issue is severe because the behaviour is odd and follows
neither other mature Lispy languages nor the reference manual.

    (info "(elisp)Lambda Expressions")

    In Emacs Lisp, such a list is valid as an expression--it evaluates
    to itself.

As I said 11 month ago, I hit on this issue a few times already.  So did
others.  In most cases I had a lambda form that was eval'ed twice due to
macro expansion.

    ;; -*- lexical-binding: t -*-

    (defmacro a ()
      (let ((l (lambda () )))
        `(funcall ,l)))

    (a)

I realise there is a technical need for lambda's to evaluate to closures
in a lexical environment.  Are there any technical reasons for lexical
closures to not self-quote?

BTW I am perfectly fine with just fixing the docs.

        Christopher





  reply	other threads:[~2013-05-28 22:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 18:47 bug#11782: 24.1; closure is not self-quoting Christopher Schmidt
2012-07-20 12:12 ` Stefan Monnier
2012-07-20 13:38   ` Christopher Schmidt
2013-02-23 14:53     ` Christopher Schmidt
2013-05-28 20:40       ` Stefan Monnier
2013-05-28 22:35         ` Christopher Schmidt [this message]
2013-05-29  0:25           ` Stefan Monnier
2013-05-29  7:05             ` Christopher Schmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obburavs@ch.ristopher.com \
    --to=christopher@ch.ristopher.com \
    --cc=11782@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).