From: Christopher Cramer <crayc@pyro.net>
Subject: Re: functional hash operations
Date: Tue, 31 Dec 2002 06:38:37 -0600 [thread overview]
Message-ID: <20021231063837.B26806@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <m34r8vf5l3.fsf@multivac.cwru.edu>; from prj@po.cwru.edu on Mon, Dec 30, 2002 at 06:29:38PM -0500
On Mon, Dec 30, 2002 at 06:29:38PM -0500, Paul Jarc wrote:
> 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?
It's hard for me to imagine any other good representation, so I don't
think it will change. OTOH if you want more operations on hash tables
it might not be a bad idea to get them included in Guile.
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
"All you have to do is tell them they are being attacked and denounce the
pacifists for lack of patriotism and exposing the country to danger. It
works the same way in any country." - Hermann Georing, 1946
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-12-31 12:38 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 [this message]
2003-01-01 21:47 ` Marius Vollmer
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=20021231063837.B26806@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
/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).