From: Roland Orre <roland.orre@neurologic.se>
Subject: How to copy hash table?
Date: Fri, 23 Jan 2004 14:58:17 +0100 [thread overview]
Message-ID: <1074866297.23547.840.camel@localhost> (raw)
In earlier guiles, where hash-tables were vectors, I used copy-tree to
copy a hash table. Now in guile-1.7 copy-tree of the hash-table gives me
the same hash table back, which I assume is correct for atomic objects.
What I want is a table where the handles are copies so when modifying the
values in the new table it won't affect the original.
I guess there exists no trick to generally copy objects.
(Of course, for now, to overcome this I'm using hash-for-each but I'm
curios about the general issue)
/Roland
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2004-01-23 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 13:58 Roland Orre [this message]
2004-01-27 15:29 ` How to copy hash table? Mikael Djurfeldt
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074866297.23547.840.camel@localhost \
--to=roland.orre@neurologic.se \
/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).