From: uzibalqa <uzibalqa@proton.me>
To: Drew Adams <drew.adams@oracle.com>
Cc: Yuri Khan <yuri.v.khan@gmail.com>, tpeplt <tpeplt@gmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: List not getting filled up
Date: Mon, 31 Jul 2023 02:03:57 +0000 [thread overview]
Message-ID: <U9Raosi9gNwDHSDCPIc0zFGMcnjux7OoXLdlC9tvP4GpHcnFCFIdRbkDTnkUQ-sNGS_VFcgr1zvH_vXZrZxx5oOdCfH7CK1L-yPdc_BzjiQ=@proton.me> (raw)
In-Reply-To: <SJ0PR10MB5488339120CB5CDD5D1144FDF305A@SJ0PR10MB5488.namprd10.prod.outlook.com>
------- Original Message -------
On Monday, July 31st, 2023 at 1:40 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > Upon further introspection I found that it makes a lot of difference
> > whether I use
> >
> > (push (copy-sequence string) result)
> > or
> > (push string result)
> >
> > Why is that ?
>
> Because of just what everyone's been saying:
>
> If you add the string to the list then you
> add the same string each time, because the
> variable `string' refers to the same Lisp object (same string), as shown by` eq'.
This is certainly defeating me.
> If you add a copy of the string the copy
> reflects the current state of the string.
string is being passed as argument to function permute, how does it not reflect
its current state ?
> As I wrote:
> (eq foo (copy-sequence foo)) ; -> nil
Could I have a real example of how they would be different ?
next prev parent reply other threads:[~2023-07-31 2:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 23:21 List not getting filled up uzibalqa
2023-07-29 11:19 ` Emanuel Berg
2023-07-30 14:28 ` tpeplt
2023-07-30 14:47 ` uzibalqa
2023-07-30 17:42 ` Yuri Khan
2023-07-31 0:06 ` uzibalqa
2023-07-31 8:55 ` Yuri Khan
2023-07-31 0:50 ` [External] : " Drew Adams
2023-07-31 1:08 ` uzibalqa
2023-07-31 1:29 ` Drew Adams
2023-07-31 1:34 ` uzibalqa
2023-07-31 1:40 ` Drew Adams
2023-07-31 2:03 ` uzibalqa [this message]
2023-07-31 2:59 ` Heime
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='U9Raosi9gNwDHSDCPIc0zFGMcnjux7OoXLdlC9tvP4GpHcnFCFIdRbkDTnkUQ-sNGS_VFcgr1zvH_vXZrZxx5oOdCfH7CK1L-yPdc_BzjiQ=@proton.me' \
--to=uzibalqa@proton.me \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tpeplt@gmail.com \
--cc=yuri.v.khan@gmail.com \
/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).