unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: Maxime Devos <maximedevos@telenet.be>,  guile-devel@gnu.org
Subject: Re: Recursive Macros generating Definitions
Date: Mon, 03 Oct 2022 22:29:28 +0200	[thread overview]
Message-ID: <87h70klkgn.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <e00a2d71-d9d3-868a-2133-fefc28c10fcd@abou-samra.fr> (Jean Abou Samra's message of "Mon, 3 Oct 2022 20:42:39 +0200")

Hey!

Jean Abou Samra wrote:
> Le 03/10/2022 à 15:41, Frank Terbeck a écrit :
>> I get the point, but I think it's sort of surprising, when everything in
>> the macro-language is  otherwise quite literal, to  my understanding. It
>> may be warranted to  point this out in the documentation  that this is a
>> side effect of hygienic macros, I think.
>
> It *is* extensively documented.
>
> https://www.gnu.org/software/guile/manual/html_node/Hygiene-and-the-Top_002dLevel.html#Hygiene-and-the-Top_002dLevel

Thanks! I had to check when that was added. I would have guessed recent-
ly, but it wasn't. …so, I guess I don't have an excuse. :)


[…]
> I think it is worth taking a look not just at the Guile documentation but also
> at the Scheme standards, which are more verbose on the details of syntax->datum
> and such. See
>
> http://www.r6rs.org/final/html/r6rs-lib/r6rs-lib-Z-H-13.html
>

Indeed. That's a nice reference, thanks! I didn't realise there was such
a document about the library section of r6rs. Useful!


Regards, Frank



      reply	other threads:[~2022-10-03 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 11:32 Recursive Macros generating Definitions Frank Terbeck
2022-10-03 12:48 ` Maxime Devos
2022-10-03 13:41   ` Frank Terbeck
2022-10-03 18:42     ` Jean Abou Samra
2022-10-03 20:29       ` Frank Terbeck [this message]

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=87h70klkgn.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=guile-devel@gnu.org \
    --cc=jean@abou-samra.fr \
    --cc=maximedevos@telenet.be \
    /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).