From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Chris Vine Newsgroups: gmane.lisp.guile.devel Subject: Re: guile 3 update, halloween edition Date: Thu, 31 Oct 2019 17:27:11 +0000 Message-ID: <20191031172711.c04c51982089d1c48a5288a0@gmail.com> References: <87o8xyhtz6.fsf@pobox.com> <20191031000130.844639594617443947637347@gmail.com> <87a79gj38q.fsf@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="180991"; mail-complaints-to="usenet@blaine.gmane.org" To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Oct 31 18:27:24 2019 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iQEEG-000kzS-M4 for guile-devel@m.gmane.org; Thu, 31 Oct 2019 18:27:24 +0100 Original-Received: from localhost ([::1]:52982 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iQEEF-0004Sp-EJ for guile-devel@m.gmane.org; Thu, 31 Oct 2019 13:27:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47944) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iQEE5-0004LE-OM for guile-devel@gnu.org; Thu, 31 Oct 2019 13:27:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iQEE4-0006Mb-Hs for guile-devel@gnu.org; Thu, 31 Oct 2019 13:27:13 -0400 Original-Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]:37777) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iQEE4-0006Lt-6k for guile-devel@gnu.org; Thu, 31 Oct 2019 13:27:12 -0400 Original-Received: by mail-wr1-x433.google.com with SMTP id t1so1222331wrv.4 for ; Thu, 31 Oct 2019 10:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=oIskARgmsZmyuiEyOstIAQk/WBglqgP8h4/2Grjw70g=; b=fdJKZ4u2eG6POqnW6nzBbff23RrsIL7q/wjTZ2MiI6Biuz496VMbNdNcCKBf0dn9AU bakVmFdaQ2XDJbkjeCyG9QZTtYhNwVhIz2KVsffTMYYvmot316iNqVnM2J8mjnU3msZ5 MyAj0grBtBcc6gyaOrSIkb3o0R88j2h4ODxBwSYd6mVqeMiXWQXaIWWRjVkhn9Ddghn6 XIQDv0EVpcTledxwocaDOwZwjfRdTeJyARPsGWQQdgzTY8MtUbRffY5l7nfNbuPNQtd0 JngyB18zlksPSS73yzJvecb1RDXYxScMTPGK/EAC4JK+7ke/Y4opKDMZ2SXWp97D9nRw fxvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=oIskARgmsZmyuiEyOstIAQk/WBglqgP8h4/2Grjw70g=; b=KtUXCQZbUq6+FWhkLZj++MGLVnU7vDGdaYwayVLtRR5RGfNPAPvdOK91iuJwYcR1HE bg6Udc1Ou8gdmlJL02oWsxafYCyWAtopU0Un9lZMA/Hfe/OyA1gxSkENlpZQscgUyBu9 RS6ik4lLpduEzMmtH+6bYjALqxd8unjqCMjQCdPryHGAkK5pLqE9mQ6m44njt7CjGC2e sQE52CGY7rE/qdANywe/CIWfl3Y+B4m9Swil4mDHr/ySOEhpHr1fGaqKyr7JN2ucT2rl aFGYUwc2ilTBAGmXNn3KzTIjvlvukD3KbvOlHO2YdCA/OICWx0CSV4S2pC5K6zEaa0Gf HfcA== X-Gm-Message-State: APjAAAW9lS/zP9LPq0H1ZY6UYy31LFr6/Hew3PFXHq1dlU4EXlrahHeu 4qfuCn3UHdJw24BKEcjDEQR4g5m/ X-Google-Smtp-Source: APXvYqxFGoiyI6EsB/imwnxeU+6qNlvUcRyuPThJaiV6IYQQGYaH0cARTtjLqHl3AusEqMzTcGkx5A== X-Received: by 2002:adf:9185:: with SMTP id 5mr7068957wri.389.1572542830606; Thu, 31 Oct 2019 10:27:10 -0700 (PDT) Original-Received: from bother.homenet ([2002:5f92:6c68:10:92c5:87ef:6ea8:1cef]) by smtp.gmail.com with ESMTPSA id j15sm3279587wrt.78.2019.10.31.10.27.09 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 31 Oct 2019 10:27:10 -0700 (PDT) Original-Received: from bother.homenet (localhost [127.0.0.1]) by bother.homenet (Postfix) with SMTP id 3B95D269296 for ; Thu, 31 Oct 2019 17:27:11 +0000 (GMT) In-Reply-To: <87a79gj38q.fsf@pobox.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::433 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:20138 Archived-At: On Thu, 31 Oct 2019 17:20:37 +0100 Andy Wingo wrote: > Greets :) > > On Thu 31 Oct 2019 01:01, Chris Vine 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? I think "exception objects" would be fine. More broadly, I view an exception as something which makes the current thread of execution follow an exceptional path (say, implemented by some kind of continuation object), used generally but not exclusively to indicate that an error has occurred. An R6RS or SRFI-35 condition object on the other hand is a structured error information service, intended to be a thing (but not the only thing) which might be propagated as the payload of the exception, and which you can conveniently match on. Chris