From: "Wette, Matthew R (3441)" <matthew.r.wette@jpl.nasa.gov>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Modifying nested dictionary/alist type data
Date: Fri, 15 Apr 2016 14:00:17 +0000 [thread overview]
Message-ID: <36EEBF8E-6848-4B9D-84EC-F7ACEDC84583@jpl.nasa.gov> (raw)
In-Reply-To: <0506AB66-CF82-4B86-A2A8-4FC144FC7D59@paulwmorris.com>
> On Apr 14, 2016, at 4:44 PM, Paul Morris <paul@paulwmorris.com> wrote:
> But if you have nested alists like this
>
> (define my-alist ‘((aaa . ((bbb . ((ccc . 10)))))))
>
> and you want to change ccc, then the “set!” trick doesn’t help. (...what would you “set!”?) So what’s the best approach here for such nested data structures? Maybe I should just use nested hash maps instead? Sorry if I’m missing something obvious.
Not sure I understand this entirely, but have you looked at boxes? Look at SRFI-111 in the Guile Reference.
next prev parent reply other threads:[~2016-04-15 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 23:44 Modifying nested dictionary/alist type data Paul Morris
2016-04-15 14:00 ` Wette, Matthew R (3441) [this message]
2016-04-15 17:20 ` Andreas Rottmann
2016-04-16 14:37 ` Paul Morris
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=36EEBF8E-6848-4B9D-84EC-F7ACEDC84583@jpl.nasa.gov \
--to=matthew.r.wette@jpl.nasa.gov \
--cc=guile-user@gnu.org \
/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).