From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: Re: Self-evaluating function and closure
Date: Mon, 17 Jun 2019 11:03:20 +0300 [thread overview]
Message-ID: <20190617080320.GA1403@newvzh.lokolhoz> (raw)
In-Reply-To: <87h88p3kpy.fsf@netris.org>
Hi Mark, John,
My fault, sorry. In a fresh session there is no toplevel
definition of the function defined by 'let'. Looking through
Geiser history I found "(define a $9)". Probably this was the
culprit. My apologies and thank you for your help!
--
Vladimir
(λ)επτόν EDA — https://github.com/lepton-eda
next prev parent reply other threads:[~2019-06-17 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 20:29 Self-evaluating function and closure Vladimir Zhbanov
2019-06-15 19:35 ` John Cowan
2019-06-16 0:39 ` Mark H Weaver
2019-06-16 0:36 ` Mark H Weaver
2019-06-16 9:02 ` Vladimir Zhbanov
2019-06-16 10:09 ` Mark H Weaver
2019-06-17 8:03 ` Vladimir Zhbanov [this message]
2019-06-16 9:47 ` Mark H Weaver
2019-06-16 10:21 ` Thomas Morley
2019-06-16 10:32 ` Mark H Weaver
2019-06-16 10:42 ` Thomas Morley
2019-06-16 11:29 ` Mark H Weaver
2019-06-17 8:48 ` Vladimir Zhbanov
2019-06-17 14:21 ` Mark H Weaver
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190617080320.GA1403@newvzh.lokolhoz \
--to=vzhbanov@gmail.com \
--cc=guile-user@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.
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).