unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thamer Al-Harbash <tmh@whitefang.com>
Subject: Re: records as s-expressions
Date: Thu, 16 Oct 2003 16:14:40 -0400 (EDT)	[thread overview]
Message-ID: <Pine.BSF.4.58.0310161613060.11955@helena.whitefang.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0310161546380.11955@helena.whitefang.com>

On Thu, 16 Oct 2003, Thamer Al-Harbash wrote:

> However a problem occurs when dealing with SMOBs or types which
> (read) cannot convert properly. How is this dealt with in data
> types like arrays? If I print an array, which contains smobs or
> records, from the REPL, how is it converted back when (read) gets
> it again?

I should add that these aren't dealt with right now. Writing back
an array with a record inside of it of course results in an error
because #< is an unknown object which isn't handled.

The only way to make everything serializable is to force SMOBs to
have a read routine associated with them even if they don't do
anything to avoid errors.

-- 
Thamer Al-Harbash
GPG Key fingerprint: D7F3 1E3B F329 8DD5 FAE3  03B1 A663 E359 D686 AA1F


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-10-16 20:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18  2:07 records as s-expressions Thamer Al-Harbash
2003-10-07 15:47 ` Marius Vollmer
2003-10-08  4:05   ` Rob Browning
2003-10-16  4:40   ` Thamer Al-Harbash
2003-10-16 19:43     ` Marius Vollmer
2003-10-16 19:59       ` Thamer Al-Harbash
2003-10-16 20:14         ` Thamer Al-Harbash [this message]
2003-10-16 20:48         ` Marius Vollmer
2003-10-16 21:40           ` Paul Jarc
2003-11-13  0:08             ` Marius Vollmer
2003-10-16 21:09         ` Neil Jerram
2003-10-16 21:56           ` Thamer Al-Harbash
2003-10-16 21:51     ` Rob Browning
2003-10-17  6:43       ` Neil Jerram

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=Pine.BSF.4.58.0310161613060.11955@helena.whitefang.com \
    --to=tmh@whitefang.com \
    /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).