From: Chris Vine <vine35792468@gmail.com>
To: guile-devel@gnu.org
Subject: Re: guile 3 update, halloween edition
Date: Thu, 31 Oct 2019 00:01:30 +0000 [thread overview]
Message-ID: <20191031000130.844639594617443947637347@gmail.com> (raw)
In-Reply-To: <87o8xyhtz6.fsf@pobox.com>
On Wed, 30 Oct 2019 21:13:49 +0100
Andy Wingo <wingo@pobox.com> wrote:
> Also: should these structured error objects be named
> exceptions or conditions? SRFI-35, R6RS, and R7RS say "conditions", but
> racket and my heart say "exceptions"; wdyt?
R6RS and R7RS speak of raising an exception, and handling the exception
in an exception handler, and racket uses similar language. According to
R6RS "when an exception is raised, an object is provided that describes
the nature of the exceptional situation. The report uses the condition
system described in library section 7.2 to describe exceptional
situations, classifying them by condition types". However, condition
objects are optional when an exception is raised - you can just as well
use a symbol, or a symbol/string pair, for simple cases.
"Condition" is a strange word for describing structured error objects,
I agree. However, I think it would be quite confusing to describe
error objects as exceptions. "Error object" or "error condition object"
seems a reasonable alternative if the bare word "condition" is thought
to be inappropriate.
next prev parent reply other threads:[~2019-10-31 0:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:13 guile 3 update, halloween edition Andy Wingo
2019-10-30 21:19 ` Christopher Lemmer Webber
2019-10-31 0:01 ` Chris Vine [this message]
2019-10-31 16:20 ` Andy Wingo
2019-10-31 17:27 ` Chris Vine
2019-10-31 1:31 ` Nala Ginrut
2019-10-31 1:47 ` Thompson, David
2019-10-31 14:17 ` Mikael Djurfeldt
2019-10-31 16:13 ` Andy Wingo
2019-10-31 14:46 ` David Pirotte
2019-10-31 16:44 ` Sjoerd van Leent
2019-11-02 5:20 ` Mark H Weaver
2019-11-02 19:33 ` Mark H Weaver
2019-11-03 19:16 ` Andy Wingo
2019-11-03 20:18 ` Mark H Weaver
2019-11-15 9:03 ` Ludovic Courtès
2019-11-15 10:23 ` Andy Wingo
2019-11-16 15:26 ` Ludovic Courtès
2019-11-17 19:33 ` 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=20191031000130.844639594617443947637347@gmail.com \
--to=vine35792468@gmail.com \
--cc=guile-devel@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).