From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Guile User <guile-user@gnu.org>
Subject: Re: Question about data structures
Date: Sat, 28 Nov 2020 03:47:19 +0100 [thread overview]
Message-ID: <22af53fd-1ea4-abf8-7ac3-ed2ed4e91de1@posteo.de> (raw)
In-Reply-To: <1308d70fcfbff31d9e8a655aa809016f15936419.camel@divoplade.fr>
Hi all!
Thank you for your plentiful replies, I did not forget you. I simply did
not get around to to answering everyone. I got something out of it. I
still need to apply it in my program and will probably discover more
things to it, like always.
Best wishes,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2020-11-28 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 18:48 Question about data structures Zelphir Kaltstahl
2020-11-22 19:45 ` divoplade
2020-11-22 20:24 ` Zelphir Kaltstahl
2020-11-22 21:00 ` divoplade
2020-11-28 2:47 ` Zelphir Kaltstahl [this message]
2020-11-22 20:58 ` kwright
2020-11-22 22:50 ` Tim Van den Langenbergh
2020-11-23 3:42 ` Taylan Kammer
2020-11-23 4:42 ` John Cowan
2020-11-23 14:54 ` [EXT] " Thompson, David
2020-11-23 9:52 ` Neil Jerram
2020-11-23 12:24 ` Dr. Arne Babenhauserheide
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=22af53fd-1ea4-abf8-7ac3-ed2ed4e91de1@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--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).