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



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


> This behaviour  is probably  explained in one  of the  ‘syntax-case’ and
> ‘datum->syntax’ examples  in the manual,  but it  wasn't clear to  me at
> all. Not sure how, but I think there's room for improvement here. :)
>
> Thanks for  clearing this up!  And feel free  to correct anything  I got
> wrong in what I wrote in the above.


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




  reply	other threads:[~2022-10-03 18:42 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 [this message]
2022-10-03 20:29       ` Frank Terbeck

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=e00a2d71-d9d3-868a-2133-fefc28c10fcd@abou-samra.fr \
    --to=jean@abou-samra.fr \
    --cc=ft@bewatermyfriend.org \
    --cc=guile-devel@gnu.org \
    --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).