From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: records as s-expressions
Date: Thu, 16 Oct 2003 22:48:26 +0200 [thread overview]
Message-ID: <87ad80rjs5.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.BSF.4.58.0310161546380.11955@helena.whitefang.com> (Thamer Al-Harbash's message of "Thu, 16 Oct 2003 15:59:21 -0400 (EDT)")
Thamer Al-Harbash <tmh@whitefang.com> writes:
> On Thu, 16 Oct 2003, Marius Vollmer wrote:
>
>> Yes.
>>
>> One other thing that just occured to me: how does 'read' find the
>> record creator from the type name?
>
> Good point. I can't see how this would work by putting it in the
> reader.
Me neither. We can't easily solve the general problem (writing _all_
record types in a readable way by default), but we could make it easy
for the user to implement readable writing for selected record types.
Something like this:
(define r (make-record-type foo '(a b) readable-record-printer))
(register-record-reader 'foo foo)
where readable-record-printer will print a record as
#,(foo a: ... b: ...)
and register-record-reader will use define-reader-ctor to be able to
read the record back in.
> Here's the real problem though:
That's not serious: this only happens because the default record
printer uses display instead of write.
> 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?
This is a separate problem; we don't need to solve it right now.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-10-16 20:48 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
2003-10-16 20:48 ` Marius Vollmer [this message]
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=87ad80rjs5.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).