unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: when and unless
Date: Fri, 01 Jul 2011 09:50:34 +0200	[thread overview]
Message-ID: <878vsia185.fsf@pobox.com> (raw)
In-Reply-To: <878vsjyouu.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 30 Jun 2011 23:46:17 +0200")

Hi :)

On Thu 30 Jun 2011 23:46, ludo@gnu.org (Ludovic Courtès) writes:

>   http://lists.r6rs.org/pipermail/r6rs-discuss/2007-March/thread.html#1856

Wow, forgot about that one ;)

> Here’s another argument: these macros are about writing imperative code,
> which, as we all know, is Evil.  As such, they are unacceptable.
>
> (Seriously though, I won’t use them but won’t complain either if they
> land in Guile.)

OK, cool.

One place you might want to use them though is in type checks for Scheme
code.  We currently don't do very much of that, but probably should in
the future.  As in:

  (define (parameter-fluid p)
    (unless (parameter? p) (wrong-type-arg p 'parameter))
    (struct-ref p 1))

The advantage of `unless' over `if' is that the wrong-type-arg is not
called in tail position, so the error message sees `parameter-fluid' on
the stack.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-07-01  7:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 10:44 when and unless Andy Wingo
2011-06-30 21:46 ` Ludovic Courtès
2011-07-01  7:50   ` Andy Wingo [this message]
2011-07-01 12:47     ` Ludovic Courtès
2011-12-05 20:23 ` Andy Wingo
2011-12-06  7:48   ` Marijn
2011-12-06  8:29     ` Alex Shinn
2011-12-06 11:17       ` David Kastrup
2011-12-06 16:25         ` Andy Wingo
2011-12-06 16:42           ` David Kastrup
2011-12-06 17:35             ` Andy Wingo
2011-12-06 22:08               ` David Kastrup
2011-12-06 23:05                 ` Chris K. Jester-Young
2011-12-07  9:23                   ` David Kastrup
2011-12-07 15:58                     ` Chris K. Jester-Young
2011-12-08  8:42                       ` David Kastrup
2011-12-08 15:34                         ` Chris K. Jester-Young
2011-12-08 16:10                           ` David Kastrup
2011-12-08 18:10                         ` Ian Price
2011-12-07 16:10         ` Chris K. Jester-Young
2011-12-06 19:05     ` Chris K. Jester-Young
2011-12-06 19:33       ` Andy Wingo
2011-12-06 14:39   ` Ludovic Courtès
2011-12-07 14:19     ` Ludovic Courtès
2011-12-07 14:27       ` David Kastrup
2012-01-07  0:16       ` Andy Wingo
2012-01-07 22:36         ` Ludovic Courtès
2012-01-20 20:19           ` 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=878vsia185.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).