From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: R7RS
Date: Tue, 09 Sep 2014 21:02:25 +0200 [thread overview]
Message-ID: <87sik0wrb2.fsf@taylan.uni.cx> (raw)
In-Reply-To: <82k35c7k6c.fsf@gmail.com> (Carlos Pita's message of "Tue, 09 Sep 2014 14:55:39 -0300")
Carlos Pita <carlosjosepita@gmail.com> writes:
> Hi all,
>
> there was a thread a couple of years ago in this list about TODOs for
> reaching R7RS (small) compliance. Just out of curiosity, what is the
> current (or planned) level of conformance? I've read some recent
> announcements about changes in the reader that further align it with
> R7RS but I'm not sure what to expect in other areas:
Hi Carlos,
There's a branch called 'r7rs' in Guile's git repository which aims for
full (or almost-full) compliance as far as I know. I think Mark Weaver
was working on it so he might be able to give clearer information on
what will be intentionally left out. That being said:
> * libraries
This is certainly being implemented on that branch.
> * records
R7RS-small records are equivalent to SRFI-9, so this is merely a matter
of making it a part of the "(scheme base)" library which is the standard
base library of R7RS-small.
> * exceptions
Given R6RS exceptions, R7RS-small exceptions are very trivial. The
`with-exception-handler', `raise', and `raise-continuable' procedures,
and the `guard' syntax, are all the same as in R6RS. The `error'
procedure is basically the same as we have in Guile's core, and
`error-object?', `error-object-message', and `error-object-irritants'
all look pretty trivial so you can bet on the r7rs branch implementing
them.
Taylan
prev parent reply other threads:[~2014-09-09 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 17:55 R7RS Carlos Pita
2014-09-09 19:02 ` Taylan Ulrich Bayirli/Kammer [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
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=87sik0wrb2.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=carlosjosepita@gmail.com \
--cc=guile-user@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).