unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org
Subject: Re: "Missing" libraries/concepts found in other languages/ecosystems?
Date: Mon, 13 Jul 2020 11:10:05 +0100	[thread overview]
Message-ID: <20200713111005.a670f4879166cdeb35bbadd6@gmail.com> (raw)
In-Reply-To: <20200711233918.3355c443aaa8d44de772e572@gmail.com>

On Sat, 11 Jul 2020 23:39:18 +0100
Chris Vine <vine35792468@gmail.com> wrote:
> On Sat, 11 Jul 2020 14:20:22 -0400
> John Cowan <cowan@ccil.org> wrote:
> > Is the intention to provide `guard` in Guile 3.x?
> 
> It's been in guile for as long as I can remember (at least since 2.0).

By the way, guile-3.0's version of 'guard' doesn't comply with
R6RS/R7RS (I think Chez scheme's 'guard' is about the only one which
does).

After correction, R6RS and R7RS require the cond conditionals to be
evaluated and the body of any cond clause to execute in the dynamic
environment in which 'guard' was called.  If there is no cond
conditional evaluating to true and no else clause, then the dynamic
environment reverts to that of the site of the exception for the
exception to be re-raised by raise-continuable.

guile doesn't do that, I think mainly for efficiency reasons.  In
guile-3.0, the cond conditionals are evaluated in the dynamic
environment in which the exception arises, and only if there is a cond
conditional evaluating to true (or an else clause) does control pass to
the dynamic environment in which 'guard' was called for the relevant
cond clause body to execute.  So as with R6RS/R7RS, where an exception
is re-raised, that is done by raise-continuable in the dynamic context
in which the exception occurred, but a different route is chosen to get
there.

I prefer guile's approach but I imagine your view is probably different.



  parent reply	other threads:[~2020-07-13 10:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.75.1594224014.21222.guile-user@gnu.org>
2020-07-08 18:22 ` "Missing" libraries/concepts found in other languages/ecosystems? Zelphir Kaltstahl
2020-07-09 18:12   ` Leo Butler
2020-07-09 19:34     ` Zelphir Kaltstahl
2020-07-10  7:39   ` Aleix Conchillo Flaqué
2020-07-10  8:14     ` Alex Sassmannshausen
2020-07-10  8:49   ` Catonano
2020-07-10 10:21     ` Chris Vine
2020-07-10 11:20       ` Catonano
2020-07-11  0:19         ` Zelphir Kaltstahl
2020-07-11  0:34           ` Zelphir Kaltstahl
2020-07-11 10:14             ` Chris Vine
2020-07-11 13:45               ` Stefan Israelsson Tampe
2020-07-11 14:46             ` Linus Björnstam
2020-07-11 10:13           ` Chris Vine
2020-07-11 18:20             ` John Cowan
2020-07-11 22:39               ` Chris Vine
2020-07-11 22:41                 ` John Cowan
2020-07-11 23:09                   ` Chris Vine
2020-07-12  1:52                     ` John Cowan
2020-07-12 20:26                       ` Chris Vine
2020-07-13 10:10                 ` Chris Vine [this message]
2020-07-12 16:08             ` Catonano
2020-07-12 16:10               ` Catonano
2020-07-12 17:46               ` John Cowan
2020-07-12 19:14               ` Chris Vine
2020-07-12 19:32                 ` Chris Vine
2020-07-14 10:32                   ` Catonano
2020-07-14 11:06                     ` Catonano
2020-07-14 16:21                     ` Chris Vine
2020-07-12 20:33               ` Zelphir Kaltstahl
2020-07-08  7:38 Simen Endsjø
2020-07-08  8:15 ` Vladimir Zhbanov
2020-07-08 10:08 ` Catonano
2020-07-08 11:29 ` Chris Vine
2020-07-10 12:15 ` Christopher Lam
2020-07-10 15:52   ` Chris Vine

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=20200713111005.a670f4879166cdeb35bbadd6@gmail.com \
    --to=vine35792468@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).