From: "Linus Björnstam" <linus.internet@fastmail.se>
To: "Damien Mattei" <damien.mattei@gmail.com>,
guile-user <guile-user@gnu.org>
Subject: Re: define anywhere
Date: Sun, 06 Jun 2021 10:09:22 +0200 [thread overview]
Message-ID: <a77de2a7-c8f7-4222-9fdb-2d13ad898b83@www.fastmail.com> (raw)
In-Reply-To: <d6fb2866-c707-4c76-aace-648bfbe42a51@www.fastmail.com>
Note however, that I seem to have forgotten when and unless. also: cond has no support for the extended "test guard => lambda" form. Neither do I believe that the any "special" case form is supported. If there is any interest whatsoever, I can implement it when I have time.
The code produced is NOT the same as guile3 does for internal defines, however.
(define a 2)
(define b 3)
(display "hej")
(define c 3)
(+ a b c)
becomes ONE letrec under gulie3, whereas my library turns it into
(letrec ((a 2) (b 3))
(display "hej")
(letrec ((c 3))
(+ a b c)))
That should be an easy fix, again if there is any interest.
--
Linus Björnstam
On Sat, 5 Jun 2021, at 17:23, Linus Björnstam wrote:
> I implemented this hack before guile 3 got defines in function bodies:
> https://hg.sr.ht/~bjoli/guile-define
>
> Even I guile 3 it allows a more liberal placement of define, but it
> won't work for things like bodies of imported macros (like match)
> --
> Linus Björnstam
>
> On Sat, 5 Jun 2021, at 00:27, Damien Mattei wrote:
> > hello,
> > i'm was considering that i want to be able to define a variable
> > anywhere in
> > code, the way Python do. Few scheme can do that (Bigloo i know)
> > ( the list here is not exact:
> > https://www.reddit.com/r/scheme/comments/b73fdz/placement_of_define_inside_lambda_bodies_in/
> > )
> > is it possible in guile to do it? i do not know, so could it be added
> > to
> > the language specification for future release?
> >
> > regards,
> > Damien
> >
>
>
next prev parent reply other threads:[~2021-06-06 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 22:27 define anywhere Damien Mattei
2021-06-05 2:10 ` Taylan Kammer
2021-06-05 8:50 ` Dr. Arne Babenhauserheide
2021-06-05 15:23 ` Linus Björnstam
2021-06-06 8:09 ` Linus Björnstam [this message]
2021-06-06 12:02 ` Dr. Arne Babenhauserheide
2021-06-06 13:36 ` Linus Björnstam
2021-06-06 16:45 ` Dr. Arne Babenhauserheide
2021-06-11 8:08 ` Damien Mattei
[not found] ` <CADEOadcwk1D9of6C1owQQSqFNRvUmA=wJKSngySbGsfdDUzoMw@mail.gmail.com>
[not found] ` <28842df5-d82b-4819-b7ad-2148265f7a83@www.fastmail.com>
2021-06-09 9:29 ` Damien Mattei
2021-06-09 10:11 ` Linus Björnstam
2021-06-11 8:15 ` Damien Mattei
2021-06-11 8:07 ` Damien Mattei
2021-06-11 23:43 ` Damien Mattei
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=a77de2a7-c8f7-4222-9fdb-2d13ad898b83@www.fastmail.com \
--to=linus.internet@fastmail.se \
--cc=damien.mattei@gmail.com \
--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).