From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org
Subject: Re: dumping arbitrary structures
Date: Mon, 26 Jan 2004 17:30:20 -0500 [thread overview]
Message-ID: <m3u12ibawd.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <1454.219.65.38.220.1075155744.squirrel@www.ezrs.com>
farazs@yapost.com wrote:
> I'm looking for something which can dump *arbitrary* guile
> structures to a byte(or scm_t_bits) array - so that they may be
> transmitted (send()) and recieved and reconstructed cleanly on the
> other end. It could also be used to save data structures to a file
> and restore them later on.
(with-output-to-string (lambda () (write object)))
That will work for built-in data types like lists, vectors, numbers,
strings, symbols, etc. User-defined records and classes are a harder
problem.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-26 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 22:22 dumping arbitrary structures farazs
2004-01-26 22:30 ` Paul Jarc [this message]
2004-01-26 23:50 ` Andreas Rottmann
2004-01-28 1:55 ` Clinton Ebadi
2004-01-28 7:39 ` farazs
2004-01-28 13:18 ` Thien-Thi Nguyen
2004-01-28 22:47 ` Clinton Ebadi
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=m3u12ibawd.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--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).