unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: cl-loop - do you understand it well?
Date: Wed, 21 Dec 2022 09:12:12 +0100	[thread overview]
Message-ID: <877cylmazn.fsf@web.de> (raw)
In-Reply-To: <87h6xr872h.fsf@dataswamp.org> (Emanuel Berg's message of "Mon, 19 Dec 2022 21:36:06 +0100")

Emanuel Berg <incal@dataswamp.org> writes:

> >   (cl-block nil
> >     (let* ((i 0)
> >            (funs nil))
> >       (while (<= i 1)
> >         (setq funs (nconc funs (list (lambda nil i))))
> >         (setq i (+ i 1)))
> >       (apply #'+ (mapcar #'funcall funs))))
> >
> No, where does the 4 come from?

There are two closures in FUNS, and both share the same lexical variable
i.  When the closures are `funcall'ed i is bound to 2, which is the
value i had when the loop is exited.  2*2=4.

The goal of this exercise was to demonstrate that closures share
modifiable environments instead of copies of values present at closure
creation time.

Michael.



      reply	other threads:[~2022-12-21  8:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  2:22 cl-loop - do you understand it well? Emanuel Berg
2022-12-10 18:56 ` Michael Heerdegen
2022-12-10 19:00   ` Akib Azmain Turja
2022-12-10 19:35     ` tomas
2022-12-10 20:48       ` Michael Heerdegen
2022-12-11  5:57         ` Akib Azmain Turja
2022-12-11 14:43           ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-12  6:03             ` Akib Azmain Turja
2022-12-12  1:41           ` Michael Heerdegen
2022-12-14 23:53             ` Emanuel Berg
2022-12-16  0:25               ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-17  0:02                 ` Emanuel Berg
2022-12-16  2:25               ` Michael Heerdegen
2022-12-17  0:03                 ` Emanuel Berg
2022-12-18  0:16                   ` Michael Heerdegen
2022-12-19 20:36                     ` Emanuel Berg
2022-12-21  8:12                       ` Michael Heerdegen [this message]

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=877cylmazn.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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).