unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Control the order of expansion of syntax-case macros
Date: Fri, 20 Dec 2024 19:38:59 +0900	[thread overview]
Message-ID: <CAPjoZod2Nip5bXOn3q8dv1xUDZQeQUMvpZe8T2MH7Q1KUV1aNA@mail.gmail.com> (raw)
In-Reply-To: <1bfa042ed3719a10006789205e954bb53c83cf45.camel@planete-kraus.eu>

>
>
> So my guess is that syntax objects are expanded lazily. Is there
> something I can do to get #'world expanded before #'hello?
>

More accurately, it's Normal Order for macro and special form (actually
it's another fancy name of internal implemented macro), you may want to
take a look through the "application order vs normal order" part inside
SICP.

Here's a simple formula to understand practical Lazy:
Lazy = Normal + Updating

"Updating" is another fancy academic term for caching the evaluated value
to prevent redundant computation. Say, memorization.

I could be blamed for the over simplified explanation to say Normal Order
rather than more general term non-strict-evaluation, Normal Order is just
one of them, theoretically, but most useful.

In your case, there's no updating, so you shouldn't claim it "Lazy" in
computation. :-)




Best regards.


  parent reply	other threads:[~2024-12-20 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 16:33 Control the order of expansion of syntax-case macros Vivien Kraus
2024-12-20  9:15 ` Maxime Devos via General Guile related discussions
2024-12-20 17:01   ` Vivien Kraus
2024-12-20 10:38 ` Nala Ginrut [this message]
2024-12-20 20:12 ` Zelphir Kaltstahl

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=CAPjoZod2Nip5bXOn3q8dv1xUDZQeQUMvpZe8T2MH7Q1KUV1aNA@mail.gmail.com \
    --to=nalaginrut@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).