From: Andy Wingo <wingo@pobox.com>
To: Chris Vine <vine35792468@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: guile 3 update, halloween edition
Date: Thu, 31 Oct 2019 17:20:37 +0100 [thread overview]
Message-ID: <87a79gj38q.fsf@pobox.com> (raw)
In-Reply-To: <20191031000130.844639594617443947637347@gmail.com> (Chris Vine's message of "Thu, 31 Oct 2019 00:01:30 +0000")
Greets :)
On Thu 31 Oct 2019 01:01, Chris Vine <vine35792468@gmail.com> writes:
> "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.
I'm very sympathetic to this argument -- an exception seems like a
thing-in-motion, not a thing-at-rest. But perhaps it's just the effect
of habit, setting up expectations about what good names are. (After
all, plenty of people seem happy with the term "condition"!)
Perhaps there is a middle ground of sorts: maybe the manual can
comprehensively describe what R6RS refers to as conditions using the
term "exception objects". WDYT?
Andy
next prev parent reply other threads:[~2019-10-31 16:20 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
2019-10-31 16:20 ` Andy Wingo [this message]
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=87a79gj38q.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=vine35792468@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).