From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: let-values, and-let* no variables
Date: Wed, 22 Sep 2004 00:09:17 +0200 [thread overview]
Message-ID: <87brfztgtu.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87llfney3a.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 07 Sep 2004 10:12:25 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>>
>> Uhh, intuitively I'd say that this is wrong behavior.
>
> One that's guile specific is let-optional and let-keywords, eg.
>
> (use-modules (ice-9 optargs))
> (let ()
> (let-keywords '() #f ()
> (define localvar 123))
> localvar)
>
> => 123
>
> which could be fixed fairly easily,
Yes, please do. Thanks!
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-09-21 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 1:27 let-values, and-let* no variables Kevin Ryde
2004-08-20 10:28 ` Marius Vollmer
2004-09-07 0:12 ` Kevin Ryde
2004-09-21 22:09 ` Marius Vollmer [this message]
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=87brfztgtu.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).