all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: 24171@debbugs.gnu.org
Subject: bug#24171: 25.1; Bytecode returns nil instead of expected closure
Date: Sun, 07 Aug 2016 13:24:51 +0200	[thread overview]
Message-ID: <87wpjs95z0.fsf@linux-m68k.org> (raw)
In-Reply-To: <2cd05bdc-37df-d215-0154-6d67636e486f@gmail.com> ("Clément Pit--Claudel"'s message of "Sun, 7 Aug 2016 05:30:31 -0400")

On So, Aug 07 2016, Clément Pit--Claudel <clement.pit@gmail.com> wrote:

> On 2016-08-07 05:01, Andreas Schwab wrote:
>> Michael Heerdegen <michael_heerdegen@web.de> writes:
>> 
>>> eval this defun:
>>>
>>> (defun test ()
>>>   (let ((my-cool-fun 'dummy))
>>>     (let ((my-cool-fun
>>>            (let ((calculate (lambda () 1)))
>>>              (lambda () (setq my-cool-fun calculate))))
>>>           (return-my-cool-fun (lambda () my-cool-fun)))
>>>       (funcall my-cool-fun)
>>>       (funcall return-my-cool-fun))))
>>>
>>> (test) evals to a closure as expected.
>> 
>> ELISP> (test)
>> *** Eval error ***  Symbol’s value as variable is void: calculate
>
> I can reproduce this. Andreas, are you missing ;; -*- lexical-binding: t; -*- ?

I was following the instructions.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  reply	other threads:[~2016-08-07 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 23:16 bug#24171: 25.1; Bytecode returns nil instead of expected closure Michael Heerdegen
2016-08-07  9:01 ` Andreas Schwab
2016-08-07  9:30   ` Clément Pit--Claudel
2016-08-07 11:24     ` Andreas Schwab [this message]
2016-08-07 22:57   ` Michael Heerdegen
2016-08-07 14:44 ` Stefan Monnier
2016-08-08  2:04 ` Stefan Monnier
2016-08-08 10:38   ` Alex Vong
2016-08-09 17:05     ` Stefan Monnier
2016-08-09  3:26   ` Michael Heerdegen
2016-08-09  3:48     ` Michael Heerdegen

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

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

  git send-email \
    --in-reply-to=87wpjs95z0.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=24171@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.