From: Jean Abou Samra <jean@abou-samra.fr>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: error Wrong type to apply: #<syntax-transformer
Date: Fri, 04 Aug 2023 10:31:53 +0200 [thread overview]
Message-ID: <aac876329d810cbe37abd0b19aa30ba8a7657c68.camel@abou-samra.fr> (raw)
In-Reply-To: <CADEOaddOQedVt6EH8XD37S4qH4XG=z+dZH34ni5a0OT38Zc0pQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Le vendredi 04 août 2023 à 10:23 +0200, Damien Mattei a écrit :
> i know what disturb me in this error, it is because the order of
> definitions has effect but i always learn (was it right?) that in
> scheme the order of definitions should have no effect on the resulting
> evaluations.
Not really, you cannot do
(define b (1+ a))
(define a 5)
either. You *can* do
(define (b) (1+ a))
(define a 5)
but that's because the definition of b does not use the binding for a, only
capture it in a lambda abstraction. The reason you cannot do
(define b (mac 1))
(define-syntax-rule (mac x) x)
is that the (mac 1) expression used in the binding of b is using the macro (at
expand time), just like in my first example it was using the variable a (at
runtime).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-04 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 9:09 error Wrong type to apply: #<syntax-transformer Damien Mattei
2023-08-03 9:36 ` Damien Mattei
2023-08-03 9:58 ` Jean Abou Samra
2023-08-03 11:01 ` Damien Mattei
2023-08-04 8:23 ` Damien Mattei
2023-08-04 8:31 ` Jean Abou Samra [this message]
2023-08-04 12:45 ` Damien Mattei
2023-08-08 19:38 ` Maxime Devos
2023-08-08 20:17 ` Damien Mattei
2023-08-08 23:00 ` Jean Abou Samra
2023-08-09 9:42 ` Maxime Devos
2023-08-09 10:25 ` Maxime Devos
2023-08-09 13:22 ` Jean Abou Samra
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=aac876329d810cbe37abd0b19aa30ba8a7657c68.camel@abou-samra.fr \
--to=jean@abou-samra.fr \
--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).