From: Dirk Herrmann <dirk@ida.ing.tu-bs.de>
Cc: Keith Wright <kwright@gis.net>,
Guile User Mailing List <guile-user@gnu.org>
Subject: Re: Problem with cond macro.
Date: Sun, 28 Apr 2002 21:46:42 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0204282143350.7904-100000@marvin.ida.ing.tu-bs.de> (raw)
In-Reply-To: <87adrqz8yd.fsf@zagadka.ping.de>
On 26 Apr 2002, Marius Vollmer wrote:
> Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:
>
> > Well, I'm not sure I understand all of this: What about the following:
> >
> > (define => #f)
> > (cond (#t => 'ok))
> >
> > Should this also deliver 'ok ? It doesn't seem to with the current
> > implementation of syncase.
>
> Syncase is not really totally integrated with the module system yet, I
> think. That's why it can be confused by top-level bindings.
OK, but can you definitely say "Yes, it should deliver 'ok" or not? I am
not sure it is said explicitly in R5RS. If a macro introduces a bound
identifier, it is renamed in the subforms. I am not sure if and how this
applies for 'define.
Best regards
Dirk Herrmann
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-04-28 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 22:41 Problem with cond macro Panagiotis Vossos
2002-04-16 8:49 ` Julian v. Bock
2002-04-16 9:45 ` Panagiotis Vossos
2002-04-16 11:10 ` Julian v. Bock
2002-04-16 15:38 ` Joshua Judson Rosen
2002-04-17 0:30 ` Panagiotis Vossos
2002-04-17 20:58 ` Neil Jerram
2002-04-20 12:21 ` Neil Jerram
2002-04-20 12:27 ` Neil Jerram
2002-04-17 5:34 ` Keith Wright
2002-04-25 21:59 ` Dirk Herrmann
2002-04-26 6:58 ` Keith Wright
2002-04-26 17:05 ` Marius Vollmer
2002-04-28 19:46 ` Dirk Herrmann [this message]
2002-05-07 18:41 ` Marius Vollmer
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=Pine.LNX.4.21.0204282143350.7904-100000@marvin.ida.ing.tu-bs.de \
--to=dirk@ida.ing.tu-bs.de \
--cc=guile-user@gnu.org \
--cc=kwright@gis.net \
/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).