From: Maxime Devos <maximedevos@telenet.be>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Fwd: [Patch] definitions in when, unless, do as well as in cond- and case-clauses
Date: Sat, 05 Feb 2022 11:55:07 +0100 [thread overview]
Message-ID: <e558354d5a91e01f07e1ac506498e2587f741fbf.camel@telenet.be> (raw)
In-Reply-To: <CAGua6m1121mTOPftLEmMm7FWU3o7vSAHZ=PEvce4pRn2wK9mVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Hi,
> > (define foo 'bar) ;; <--- ^^^
> > (define-syntax foobar
> > (syntax-rules (foo)
> > ((_ foo)
> > (begin (pk "it's a foo!") foo))
> > ((_ goo)
> > (begin (pk "it's not a foo ...") goo))))
> >
> > (define (zebra stripes)
> > (if stripes
> > (define foo 'quux)) ;; <--- ###
> > (foobar foo)) ;; <--- ***
Stefan Israelsson Tampe schreef op za 05-02-2022 om 02:14 [+0100]:
> For conditional variables you gave a default value.
I don't understand the question, I didn't give a default value?
The variable 'foo' (^^^) is a different variable from 'foo' (###)
since 'foo' (^^^) is a module variable, and 'foo' (###) is a local
variable in 'zebra'. Merely having the same name does not imply
being the same variable, c.f. shadowing, so '^^^' does _not_ give
a default value to the 'foo' in '###'.
(If '###' was 'set!' instead of 'define', then the two variables would
have been the same.)
> So then why on earth do you not have an implicit let ?
> There must be a good reason.
I don't understand the question, there's an implicit 'let' here:
the definition of 'zebra'. Also, I don't see what the question ‘why do
you not have an implicit let?’ has to do with ‘For conditional
variables you gave a default value.’.
Also, AFAICT these questions don't seem to have anything to do
with the macro system problems I noted?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-05 10:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 19:11 [Patch] definitions in when, unless, do as well as in cond- and case-clauses Linus Björnstam
2021-06-17 9:06 ` Maxime Devos
2021-06-17 12:57 ` Linus Björnstam
2021-06-17 13:54 ` Maxime Devos
2022-02-03 10:48 ` Linus Björnstam
[not found] ` <CAGua6m1Cqe=aLOD7-jfzoqxP1aOxvWn3=UgcKyk+Dx7_51Bq3w@mail.gmail.com>
2022-02-04 20:11 ` Fwd: " Stefan Israelsson Tampe
2022-02-04 20:58 ` Maxime Devos
[not found] ` <CAGua6m11r27x=rq4S4fF09vHY+S-Az7GOZfmoT41hEBDSkLJQg@mail.gmail.com>
2022-02-04 21:40 ` Fwd: " Stefan Israelsson Tampe
2022-02-04 23:39 ` Maxime Devos
2022-02-05 1:14 ` Stefan Israelsson Tampe
2022-02-05 10:55 ` Maxime Devos [this message]
2022-02-05 17:31 ` Stefan Israelsson Tampe
2022-02-05 17:36 ` Maxime Devos
2022-02-06 6:44 ` Linus Björnstam
2022-02-06 9:27 ` tomas
2022-02-06 9:40 ` Maxime Devos
2022-02-06 9:45 ` Linus Björnstam
2022-02-06 10:48 ` tomas
2022-02-06 20:13 ` Stefan Israelsson Tampe
2022-02-06 20:28 ` Maxime Devos
2022-02-06 20:31 ` tomas
[not found] ` <CAGua6m3BHMXOhT3PHZcxdqHqHomTFESO31j5CcSNK3pbA7K-Kg@mail.gmail.com>
2022-02-06 21:26 ` Maxime Devos
2022-02-06 21:27 ` Maxime Devos
2022-02-07 5:56 ` Linus Björnstam
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=e558354d5a91e01f07e1ac506498e2587f741fbf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.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).