unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Damien Mattei <damien.mattei@gmail.com>,
	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 19:00:13 +0200	[thread overview]
Message-ID: <b1c4073b-dbdf-e60c-ca7c-4088d8b6ef5d@telenet.be> (raw)
In-Reply-To: <CADEOadf5pS917wVJhrNtMU7N_-3=g71CEeRKai+-NZMXsVE1BQ@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 902 bytes --]


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))

is allowed by the standard and that it could be meaningful.

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

If 'let' was replaced by 'begin', then it would have different semantics.

Greetings,
Maxime.


[-- Attachment #1.1.1.2: Type: text/html, Size: 1809 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-08-27 17:00 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 [this message]
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             ` 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=b1c4073b-dbdf-e60c-ca7c-4088d8b6ef5d@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=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).