[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problems with Emacs 28
From: |
Michael Heerdegen |
Subject: |
Re: problems with Emacs 28 |
Date: |
Tue, 27 Oct 2020 11:22:06 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> destructive - changes the value in the actual argument variables.
> It would seem this requires "call by name" or "call by reference", not
> "call by value", right? (Unless the value is a memory location,
> perhaps...)
"Might change a passed value". This is possible in Elisp when the value
is a sequence for example (unless the value is nil - remember your
not-in-place problem?). `setcar' receives a cons value and modifies it.
Eieio objects and even closures are other examples.
Michael.
- Re: problems with Emacs 28, (continued)
- Re: problems with Emacs 28, Michael Heerdegen, 2020/10/24
- Re: problems with Emacs 28, Emanuel Berg, 2020/10/24
- Re: problems with Emacs 28, Michael Heerdegen, 2020/10/25
- RE: problems with Emacs 28, Drew Adams, 2020/10/25
- Re: problems with Emacs 28, Emanuel Berg, 2020/10/26
- Re: problems with Emacs 28,
Michael Heerdegen <=
- Re: problems with Emacs 28, Jens C . Jensen, 2020/10/28
- Re: problems with Emacs 28, Emanuel Berg, 2020/10/28
- Re: problems with Emacs 28, Stefan Monnier, 2020/10/28
- Re: problems with Emacs 28, Emanuel Berg, 2020/10/31
Re: problems with Emacs 28, Eli Zaretskii, 2020/10/23
Re: problems with Emacs 28, Stefan Monnier, 2020/10/23
Re: problems with Emacs 28, Gregory Heytings, 2020/10/23