From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Re: functional hash operations
Date: 01 Jan 2003 22:47:59 +0100 [thread overview]
Message-ID: <877kdoh78w.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m34r8vf5l3.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Sometimes it would be useful to have functional operations on hashes:
> "make a copy of this hash which also has this additional entry", etc.
> It would also be nice to make such copies share as much memory as
> possible with the original hash. This is easy enough to do by taking
> advantage of the knowledge of the representation of hashes as vectors
> of alists, but is it safe to assume that representation? Or might the
> representation change in the future?
The hash table implementation should be considered opaque (except for
the handles) and if you want to play it safe, you should only use the
procedures from the reference manual with them.
Would it be workable to implement functional hash tables from scratch,
without basing them on the builtin implementation? There are the
functions 'hash', 'hashv', and 'hashq' to help with computing hash
values for Scheme objects.
Or, as Thien-Thi has said, you can lobby the Guile developers to
include the things you need. A working patch (also for the manual) is
quite convincing.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-01-01 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 23:29 functional hash operations Paul Jarc
2002-12-31 0:41 ` Thien-Thi Nguyen
2002-12-31 21:26 ` Paul Jarc
2003-01-01 0:48 ` Christopher Cramer
2003-01-02 6:18 ` Paul Jarc
2002-12-31 12:38 ` Christopher Cramer
2003-01-01 21:47 ` Marius Vollmer [this message]
2003-01-02 19:09 ` Paul Jarc
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=877kdoh78w.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.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.
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).