unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Taylan Kammer <taylan.kammer@gmail.com>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: Jean-Paul Roy <jean-paul.roy@unice.fr>,
	guile-devel <guile-devel@gnu.org>
Subject: Re: new function
Date: Thu, 23 Sep 2021 22:48:19 +0200	[thread overview]
Message-ID: <8dbf9ce5-f01c-94ae-40a2-0fae688f856b@gmail.com> (raw)
In-Reply-To: <9c058f24-5b15-417a-17ff-10bc13fed12d@gmail.com>

Responding to myself:

On 23.09.2021 22:27, Taylan Kammer wrote:

> I can't seem to find syntax-local-binding in Guile 2.2 or 3.0.  Did you
> have to import some special module, or are you using another version?

Worked when I imported (system syntax internal).

> Either way, I suspect that the following will not work with your macro:
> 
>   (let ()
>     (let ()
>       (<$ x 1))
>     (display x)
>     (newline))

Indeed it doesn't work, though for a different reason:

  While compiling expression:
  Syntax error:
  unknown file:43:8: body should end with an expression in form (let () (<$ x 1))

That's because indeed the inner let expands into:

  (let ()
    (define x 1))

And there has to be at least one expression after the define.  So I tried:

  (let ()
    (let ()
      (<$ x 1)
      (newline))
    (display x)
    (newline))

And as I expected, it says 'x' is unbound:

  ;;; <stdin>:44:45: warning: possibly unbound variable `x'
  <$ : global scope : x
  
  ice-9/boot-9.scm:1685:16: In procedure raise-exception:
  Unbound variable: x

The only way it will work is if you never use nested scopes, but that will
lead to very strange Scheme code, and there will probably be many cases
where you accidentally use a nested scope without immediately noticing it.

Note also that definitions aren't allowed everywhere.  Consider this:

  (let ()
    (if 'whatever
        (<$ x 1)
        (<$ x 2))
    (display x)
    (newline))

It leads to:

  While compiling expression:
  Syntax error:
  unknown file:49:17: definition in expression context, where definitions are not allowed, in form (define x 1)

Because the arms of 'if' aren't allowed to be definitions.

-- 
Taylan



  parent reply	other threads:[~2021-09-23 20:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19  7:54 new function Damien Mattei
2021-09-19 14:41 ` Matt Wette
2021-09-19 14:43   ` Matt Wette
2021-09-19 21:38 ` Taylan Kammer
2021-09-21 12:26   ` Damien Mattei
2021-09-22  8:44   ` Damien Mattei
2021-09-22  9:06     ` William ML Leslie
2021-09-22  9:53       ` Damien Mattei
2021-09-22 18:51         ` Taylan Kammer
2021-09-22 21:52           ` William ML Leslie
2021-09-23  8:40             ` Damien Mattei
2021-09-23 19:03             ` Taylan Kammer
2021-09-23 17:27           ` Damien Mattei
2021-09-23 18:00             ` Maxime Devos
2021-09-23 20:27             ` Taylan Kammer
2021-09-23 20:42               ` Damien Mattei
2021-09-23 20:48               ` Taylan Kammer [this message]
2021-09-23 21:53                 ` Damien Mattei
2021-09-24  4:41                   ` 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=8dbf9ce5-f01c-94ae-40a2-0fae688f856b@gmail.com \
    --to=taylan.kammer@gmail.com \
    --cc=damien.mattei@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=jean-paul.roy@unice.fr \
    /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).