From: Thamer Al-Harbash <tmh@whitefang.com>
Subject: Re: records as s-expressions
Date: Thu, 16 Oct 2003 00:40:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.58.0310160030340.3176@helena.whitefang.com> (raw)
In-Reply-To: <87llrxcan4.fsf@zagadka.ping.de>
On Tue, 7 Oct 2003, Marius Vollmer wrote:
Thanks Rob and Marius for your earlier comments.
> Depends on your implementation...
I planned the way I want to implement it today and would like to
know if there are any objections to my thoughts below.
> I see two choices: follow Common Lisp and use #S(<type> ...), or
> follow SRFI-10 and use something like #,(record <type> ...). I don't
> think there is any SRFI that specifies a concrete read syntax for
> records.
>
> We already use #s for uniform arrays, but overwrite it when (srfi
> srfi-4) is loaded... #S is free, tho.
Would it be reasonable to just use (read-hash-extend) to hook
into the existing reader, and as well as modify existing
boot-9.scm code cause records to (display) as #S(...)?
If I went with the SRFI-10 solution I'd be implementing this as a
(record-serialize) (record-unserialize) which seem a bit less
Schemeish to me.
If there's no objections to this I should be able to write it
Real Soon Now with minimal hassle.
--
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
next prev parent reply other threads:[~2003-10-16 4:40 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 [this message]
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
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.0310160030340.3176@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).