From: Andy Wingo <wingo@pobox.com>
To: Julian Graham <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: r6rs incompatibilities
Date: Fri, 21 May 2010 19:15:18 +0200 [thread overview]
Message-ID: <m3vdahxjkp.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTin08Cno9VGI940LzUtaKNJtIlfpfrtMzcm0CLDL@mail.gmail.com> (Julian Graham's message of "Fri, 21 May 2010 08:47:33 -0400")
Hi,
On Fri 21 May 2010 14:47, Julian Graham <joolean@gmail.com> writes:
>> * The R6RS specifies many situations in which a conforming
>> implementation must signal a specific error. Guile doesn't really
>> care about that too much -- if a correct R6RS program would not hit
>> that error, we don't bother checking for it.
>
> In a lot of these cases, that's because our libraries simply re-export
> bindings from Guile's core library or an SRFI. Instead of changing
> the error-signaling of the original procedures, we could wrap them a
> bit more in the relevant libraries to add argument validation, say, or
> to re-throw Guile's core errors as R6RS exceptions.
Sure; we'll probably take them case-by-case, accomodating where it makes
sense and documenting the incompatibility where it doesn't. It's not
like Guile's exception protocol is particularly well-thought-out :P
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-05-21 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:54 r6rs incompatibilities Andy Wingo
2010-05-21 12:47 ` Julian Graham
2010-05-21 17:15 ` Andy Wingo [this message]
2010-05-23 15:35 ` Julian Graham
2010-05-23 16:02 ` Mike Gran
2010-05-23 17:24 ` Julian Graham
2010-05-23 20:52 ` Andy Wingo
2010-05-23 21:26 ` Andy Wingo
2010-05-26 13:02 ` Julian Graham
2010-05-26 13:21 ` Andy Wingo
2010-05-26 16:43 ` Ludovic Courtès
2010-05-27 8:06 ` Andy Wingo
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=m3vdahxjkp.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=joolean@gmail.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).