From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Mark H Weaver" <mhw@netris.org>,
"Ludovic Courtès" <ludo@gnu.org>,
11198@debbugs.gnu.org,
"Klaus Stehle" <klaus.stehle@uni-tuebingen.de>
Subject: bug#11198: problems reading data with a "read-hash-extend" registered reader
Date: Tue, 24 Apr 2012 07:24:18 -0400 [thread overview]
Message-ID: <CA+U71=PSKaRE_xeLkDgu1Pyu7a6rBgKCH6yJJYfnw-2pPVNXwg@mail.gmail.com> (raw)
In-Reply-To: <87lillwnvl.fsf@pobox.com>
Hello,
>> I think the reader should only return valid Scheme objects that have a
>> read syntax (info "(r5rs) Lexical Structure"), and records are not among
>> them.
>
> I agree, FWIW.
This seems like circular logic to me - extending the reader should
mean that new types can have read syntax. The problem here, I think,
is that the compiler also needs to know how to serialize those types.
Why don't we provide an interface to define a serializer as well as a
reader, and have compile-assembly use these serializers? As long as
each type has both a serializer and a reader, it should work fine.
That also feels symmetrical, which I take as a good sign. :-)
Noah
next prev parent reply other threads:[~2012-04-24 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 20:16 bug#11198: problems reading data with a "read-hash-extend" registered reader Klaus Stehle
2012-04-09 21:10 ` Ludovic Courtès
2012-04-11 19:07 ` Klaus Stehle
2012-04-11 19:33 ` Mark H Weaver
2012-04-11 20:34 ` Klaus Stehle
2012-04-22 13:43 ` Mark H Weaver
2012-04-22 18:01 ` Ludovic Courtès
2012-04-24 8:11 ` Andy Wingo
2012-04-24 11:24 ` Noah Lavine [this message]
2012-04-24 11:38 ` Noah Lavine
2012-04-24 16:22 ` Ludovic Courtès
2012-07-05 8:00 ` bug#11198: prefab structs in guile Andy Wingo
[not found] ` <877gui7i3y.fsf@pobox.com>
2012-07-05 20:57 ` Ludovic Courtès
[not found] ` <87ipe2dizn.fsf@gnu.org>
2012-07-05 21:06 ` Andy Wingo
[not found] ` <878vex534f.fsf@pobox.com>
2012-07-05 21:55 ` Ludovic Courtès
[not found] ` <874npldga9.fsf@gnu.org>
2012-07-05 22:03 ` Andy Wingo
2012-07-05 22:06 ` Andy Wingo
[not found] ` <87ipe13lya.fsf@pobox.com>
2012-07-05 22:14 ` Ludovic Courtès
[not found] ` <87a9zdc0tc.fsf@gnu.org>
2012-11-27 21:52 ` Ludovic Courtès
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='CA+U71=PSKaRE_xeLkDgu1Pyu7a6rBgKCH6yJJYfnw-2pPVNXwg@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=11198@debbugs.gnu.org \
--cc=klaus.stehle@uni-tuebingen.de \
--cc=ludo@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).