From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Appending lists
Date: Sat, 19 Jun 2021 22:07:44 +0000 [thread overview]
Message-ID: <SA2PR10MB4474639723D35B6AEDDB4F69F30C9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87fsxdzgl9.fsf@zoho.eu>
> >> Then these terms should be dropped, perhaps.
> >
> > Relative terms are (relatively) useful. Would you drop
> > "left" or "right" or "up" or "down"?
>
> Yes, but everyone knows that, however when someone introduces
> fancy terminology (shallow and deep copy) one expects them to
> have precise definitions.
>
> At least that's what I expected in this case, maybe that's
> relative as well...
They're common, old, general, and (yes) relative terms.
And hardly fancy. But if unacquainted (no shame in that):
https://letmegooglethat.com/?q=deep+copy+lisp
https://letmegooglethat.com/?q=shallow+copy+lisp
This heavily upvoted Q&A is the first search hit:
https://stackoverflow.com/questions/184710/what-is-the-difference-between-a-deep-copy-and-a-shallow-copy
next prev parent reply other threads:[~2021-06-19 22:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 3:18 Appending lists Drew Adams
2021-06-17 7:48 ` tomas
2021-06-18 23:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-18 23:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-19 6:57 ` tomas
2021-06-19 21:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-19 22:07 ` Drew Adams [this message]
2021-06-20 19:50 ` [External] : " Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 19:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 20:10 ` Jean Louis
2021-06-20 20:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 19:59 ` Jean Louis
2021-06-20 20:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 20:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 20:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 21:49 ` Jean Louis
2021-06-20 22:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 23:30 ` Jean Louis
2021-06-21 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 21:46 ` Jean Louis
2021-06-20 22:09 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20 23:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 23:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-06-16 14:16 Drew Adams
2021-06-16 17:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-16 18:00 ` Drew Adams
2021-06-14 16:36 Pierpaolo Bernardi
2021-06-14 16:40 ` henri-biard
2021-06-14 18:21 ` Alexandr Vityazev
2021-06-15 0:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-15 8:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-15 9:18 ` tomas
2021-06-16 1:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-16 7:28 ` tomas
2021-06-16 16:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-16 16:55 ` [External] : " Drew Adams
2021-06-16 17:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-16 17:54 ` Drew Adams
2021-06-16 23:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-17 7:54 ` tomas
2021-06-18 23:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=SA2PR10MB4474639723D35B6AEDDB4F69F30C9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).