From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: Re: cos -> goops, maybe not?
Date: Tue, 01 Sep 2009 17:08:00 -0000 [thread overview]
Message-ID: <4A9D54FE.4000104@sebabeach.org> (raw)
In-Reply-To: <4A9D52DF.7060108@sebabeach.org>
Doug Evans wrote:
> I've been looking through r6rs (r6rs.org) and various Scheme
> implementations.
>
> As far as moving to goops, the higher order bit to me is to be able to
> run cgen on multiple Scheme implementations.
>
> I still think we should replace cos, or at least slim it down and
> simplify it (and keep it r5rs (or r6rs) compatible).
> OTOH, it might be nice to have something that can advantage of the
> underlying data structure support of particular Scheme
> implementations, it would presumably help when printing objects for
> example.
>
> Anyways,
> fyi.
>
Maybe use r6rs's "records" as a model?
We could use the native implementation where preferable, and we can
provide an implementation of the subset of it that we use.
prev parent reply other threads:[~2009-09-01 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 16:59 Doug Evans
2009-09-01 17:08 ` Doug Evans [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9D54FE.4000104@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.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).