unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Sascha Ziemann <ceving@gmail.com>
To: guile-user@gnu.org
Subject: Re: Does declaration order matter in guile?
Date: Mon, 13 Feb 2023 09:05:40 +0100	[thread overview]
Message-ID: <CAGUt3y6hGkNKpgM_26cPr6obOmLxmLjRUgBTJ1VWWhAhPNqMzA@mail.gmail.com> (raw)
In-Reply-To: <3c8f41c0-2978-1ab8-b265-a8ab59030929@gmail.com>

Am So., 12. Feb. 2023 um 20:52 Uhr schrieb Taylan Kammer
<taylan.kammer@gmail.com>:
>
> On 12.02.2023 19:46, wolf wrote:
>
> > 1. When does order matter? What is going on here?
>
> The order matters in this case because the SRFI-9 implementation in Guile defines
> syntax (macros) rather than just variables bound to procedures.

This is a huge problem of Scheme in general, that you can not
distinguish between
procedures and macros just by looking at the code. You have to know it
or you have
to look it up in the manual.

You also can not ask Scheme about macros, because macros are not
first-class-citizens.
This might be interesting:
https://matt.might.net/articles/metacircular-evaluation-and-first-class-run-time-macros/



  reply	other threads:[~2023-02-13  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 18:46 Does declaration order matter in guile? wolf
2023-02-12 19:52 ` Taylan Kammer
2023-02-13  8:05   ` Sascha Ziemann [this message]
2023-02-13 10:44     ` Dr. Arne Babenhauserheide
2023-02-13 17:07     ` Maxime Devos
2023-02-14 20:00   ` wolf
2023-02-14 20:26     ` Dr. Arne Babenhauserheide
2023-02-13 17:10 ` Maxime Devos

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=CAGUt3y6hGkNKpgM_26cPr6obOmLxmLjRUgBTJ1VWWhAhPNqMzA@mail.gmail.com \
    --to=ceving@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).