From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: guile 2.0?
Date: Sun, 25 Aug 2013 22:26:00 -0000 [thread overview]
Message-ID: <m3li3pjtkl.fsf@seba.sebabeach.org> (raw)
Now that Guile 2.0 has been out for awhile, anyone mind if we update
cgen to require it?
There are some non-upward-compatible changes I'm seeing in 2.0.9,
and I'm not sure we need to support 1.6 or 1.8 any longer.
I can also imagine taking advantage of some newer features, but at least
for a first step I'd like to get cgen usable with the latest Guile.
[Whether to stick with R*RS or use some Guile-specific features
is a good question, I'm leaning towards R*RS though I always imagined
replacing cos.scm with something like goops.]
reply other threads:[~2013-08-25 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3li3pjtkl.fsf@seba.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).