From: Damien Mattei <damien.mattei@gmail.com>
To: guile-devel <guile-devel@gnu.org>, guile-user <guile-user@gnu.org>
Subject: Fwd: expression and definition context in Scheme
Date: Mon, 29 Aug 2022 12:10:00 +0200 [thread overview]
Message-ID: <CADEOadf5btcxL8ewhd0QP_6OBBgLe9bSXLPAP5YTS0QNJUOkAw@mail.gmail.com> (raw)
In-Reply-To: <CADEOadfKR_u3qS5N5MwRuCRTxPjKi_wyWzgv-xJJ96e56X2meg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
---------- Forwarded message ---------
From: Damien Mattei <damien.mattei@gmail.com>
Date: Mon, Aug 29, 2022 at 12:09 PM
Subject: Re: expression and definition context in Scheme
To: Maxime Devos <maximedevos@telenet.be>
yes , the same with 'while too, i will make it in my Scheme+ to allow inner
'define in those blocks without other stuff (in Scheme+ i had already a
simple macro : (& ev ...) = (let () ev ...) that replace 'begin when
'define is needed in blocks.
regards,
Damien
On Sun, Aug 28, 2022 at 11:30 AM Maxime Devos <maximedevos@telenet.be>
wrote:
> On 28-08-2022 08:40, Damien Mattei wrote:
>
> in fact my thought was not clear, perhaps just allow a 'define in an
> instructions as 'when in my example , 'define-ed variable would then be
> local one in the block of 'when, will it change something in scheme
> implementation in a bad way?
>
> Are you asking for 'when' to implicitly wrap its body in a (let () ...)?
>
> If so, that's trivial to implement, without changing the Scheme
> implementation:
>
> (define-syntax-rule (when cond exp ...)
> (if cond
> (let () exp ...)))
>
> Greetings,
> Maxime.
>
[-- Attachment #2: Type: text/html, Size: 2347 bytes --]
next prev parent reply other threads:[~2022-08-29 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 16:48 expression and definition context in Scheme Damien Mattei
2022-08-27 17:00 ` Maxime Devos
2022-08-27 19:02 ` Damien Mattei
2022-08-27 19:14 ` Maxime Devos
2022-08-27 19:20 ` Maxime Devos
[not found] ` <CADEOadfCCLaqEvzLYUzEYhg94pqN3r9=c6LT=FmCivJsPudUzg@mail.gmail.com>
[not found] ` <b95df274-b727-5bb9-4657-f263a837e0f1@telenet.be>
[not found] ` <CADEOadfKR_u3qS5N5MwRuCRTxPjKi_wyWzgv-xJJ96e56X2meg@mail.gmail.com>
2022-08-29 10:10 ` Damien Mattei [this message]
2022-08-30 10:47 ` Linus Björnstam
2022-08-31 7:01 ` Damien Mattei
2022-08-31 15:29 ` Maxime Devos
2022-09-01 20:21 ` Damien Mattei
2022-09-04 8:08 ` Damien Mattei
2022-09-07 23:12 ` Aleix Conchillo Flaqué
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=CADEOadf5btcxL8ewhd0QP_6OBBgLe9bSXLPAP5YTS0QNJUOkAw@mail.gmail.com \
--to=damien.mattei@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).