From: Damien Mattei <damien.mattei@gmail.com>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: expression and definition context in Scheme
Date: Sat, 27 Aug 2022 21:02:16 +0200 [thread overview]
Message-ID: <CADEOadeSNAL6sk_cxGUkWq_d-h0ubnvSTri7j9prexMRk-9W-w@mail.gmail.com> (raw)
In-Reply-To: <b1c4073b-dbdf-e60c-ca7c-4088d8b6ef5d@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
hello Maxime,
On Sat, Aug 27, 2022 at 7:00 PM Maxime Devos <maximedevos@telenet.be> wrote:
>
> On 27-08-2022 18:48, Damien Mattei wrote:
>
> My ideas is as it is so easy to cheat the compiler
>
> I don't think it's cheating or abusive.
>
> from seeing the expressio context why does the compiler restrict this?
> expression and defintion context, i'm not sure they are in scheme
> standarts, are they really usefull?
> why not remove this from Scheme at all?
>
> I haven't read the RnRS closely, but I doubt that
>
> (some-procedure (define foo 0) (define bar 0))
>
? i do not understand well the meaning
> is allowed by the standard and that it could be meaningful.
>
in fact just allow 'define that act locally ,see my comment below
> Also, even if (begin ...) and (let () ...) where unified, it would be a
> shame to lose the ability to only have some definitions temporarily:
>
> (define foo 0)
>
> (let ((foo 0))
> whatever-something-using-the-inner-foo)
>
> something-using-the-outer-foo-again
>
i do not propose foo to overwrite the global one , just to allow local
define that have a local (in the block) range.
> If 'let' was replaced by 'begin', then it would have different semantics.
>
> Greetings,
> Maxime.
>
Regards,
Damien
[-- Attachment #2: Type: text/html, Size: 3053 bytes --]
next prev parent reply other threads:[~2022-08-27 19:02 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 [this message]
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 ` Fwd: " Damien Mattei
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=CADEOadeSNAL6sk_cxGUkWq_d-h0ubnvSTri7j9prexMRk-9W-w@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).