From: Michael Heerdegen <michael_heerdegen@web.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Xu Chunyang <mail@xuchunyang.me>, 34975@debbugs.gnu.org
Subject: bug#34975: 26.1.92; In backquote, the comma marker does not work with variable name started with dot
Date: Wed, 27 Mar 2019 02:50:14 +0100 [thread overview]
Message-ID: <87ef6t13xl.fsf@web.de> (raw)
In-Reply-To: <mvmmulit17p.fsf@suse.de> (Andreas Schwab's message of "Tue, 26 Mar 2019 10:49:14 +0100")
Andreas Schwab <schwab@suse.de> writes:
> On Mär 26 2019, Michael Heerdegen <michael_heerdegen@web.de> wrote:
>
> > But if you destructively modify the result of the backquote expression,
> > you may also change Y destructively (but not X). Things like these
> > might be clear if you come from Common Lisp, but it's all not obvious
> > IMHO.
>
> You need always be careful when destructively modifying structures,
> independent of how they were computed.
What I wanted to say was that it can be surprising that splicing may
reuse conses at all (it had been to me). The manual only tells that the
elements of the spliced list "become elements of the result". I had to
learn it the hard way. I had been careful, but I just didn't expect a
problem in that situation.
Michael.
next prev parent reply other threads:[~2019-03-27 1:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:19 bug#34975: 26.1.92; In backquote, the comma marker does not work with variable name started with dot Xu Chunyang
2019-03-24 15:16 ` Michael Heerdegen
2019-03-25 0:06 ` Drew Adams
2019-03-25 1:33 ` Michael Heerdegen
2019-03-25 14:21 ` Drew Adams
2019-03-26 0:03 ` Michael Heerdegen
2019-03-26 9:49 ` Andreas Schwab
2019-03-27 1:50 ` Michael Heerdegen [this message]
2019-04-04 3:31 ` Noam Postavsky
2019-04-04 13:10 ` Eli Zaretskii
2019-04-04 13:25 ` Noam Postavsky
2019-04-04 22:28 ` Basil L. Contovounesios
2019-04-04 23:37 ` Noam Postavsky
2019-04-05 1:15 ` Basil L. Contovounesios
2019-04-05 6:21 ` Eli Zaretskii
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=87ef6t13xl.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34975@debbugs.gnu.org \
--cc=mail@xuchunyang.me \
--cc=schwab@suse.de \
/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).