From: Noah Lavine <noah.b.lavine@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: [PATCH] Improved source properties and errors; => within case
Date: Wed, 8 Feb 2012 16:27:58 -0500 [thread overview]
Message-ID: <CA+U71=M54MgY3qXRuTGtpS-HyunU7DAiEuQkNvHyO8MG8_m5FA@mail.gmail.com> (raw)
In-Reply-To: <87bop98fmf.fsf@netris.org>
Hello,
> Hmm. I don't know if this is what you meant, but it occurs to me that
> as I've currently implemented them, both (cond (else (define x 5) x))
> and (case 1 (else (define x 5) x)) are allowed. I'll have to make sure
> that those raise errors. I guess that means I'll have to insert a '#f'
> like I did for local-eval. Do you see a better way?
This makes me think that we should have a macro called
expression-context for putting things in expression context. It's not
that it's hard to insert #f, but that makes the source code less clear
unless people know why a random `#f' would appear in the code. What
does everyone else think?
Noah
next prev parent reply other threads:[~2012-02-08 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 9:09 [PATCH] Improved source properties and errors; => within case Mark H Weaver
2012-02-08 10:06 ` Andy Wingo
2012-02-08 16:16 ` Mark H Weaver
2012-02-08 21:27 ` Noah Lavine [this message]
2012-02-08 22:30 ` Mark H Weaver
2012-02-10 15:45 ` Ludovic Courtès
2012-02-11 20:23 ` Mark H Weaver
2012-02-11 21:08 ` Ludovic Courtès
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='CA+U71=M54MgY3qXRuTGtpS-HyunU7DAiEuQkNvHyO8MG8_m5FA@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).