unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Walter Lewis via General Guile related discussions <guile-user@gnu.org>
To: guile-user@gnu.org
Subject: Breaking hygiene with syntax-rules?
Date: Thu, 10 Aug 2023 22:35:09 -0400	[thread overview]
Message-ID: <dada39cb-05ad-0770-be80-87597b215d16@mailbox.org> (raw)

Hi guile,

Consider this program:

(define-syntax unhygienic
   (syntax-rules ()
     ((_ the-pair fetch)
      (begin
        (define the-head (car the-pair))
        (define (fetch) the-head)))))

(unhygienic '(1) fetch1)
(unhygienic '(2) fetch2)

(fetch1)

;; => 2

It seems that the second call to unhygienic shadows the previous 
definition of the-head. I expected syntax-rules to generate fresh names 
for it each time.

Is this expected, and if so, is there any way to generate an internal 
definition using syntax-rules? For my case, I was writing a macro to 
generate SRFI-9 record definitions, but I noticed some of the getters 
and setters which I intended to be private were shadowing each other.

Best,

Walter


             reply	other threads:[~2023-08-11  2:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  2:35 Walter Lewis via General Guile related discussions [this message]
2023-08-11  5:07 ` Breaking hygiene with syntax-rules? Dr. Arne Babenhauserheide
2023-08-11  8:00 ` Jean Abou Samra
2023-08-11  8:33   ` Dr. Arne Babenhauserheide
2023-08-11 23:57     ` Jean Abou Samra
2023-08-12  5:57       ` Dr. Arne Babenhauserheide
2023-08-11 13:34   ` Walter Lewis via General Guile related discussions
2023-08-11 22:50     ` Walter Lewis via General Guile related discussions
2023-08-11 23:55       ` Jean Abou Samra
2023-08-11 23:57         ` Jean Abou Samra
2023-08-12  0:19           ` Walter Lewis
2023-08-12  0:58             ` Jean Abou Samra
2023-08-12  5:59             ` Dr. Arne Babenhauserheide
2023-08-14 19:26               ` Thompson, David

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=dada39cb-05ad-0770-be80-87597b215d16@mailbox.org \
    --to=guile-user@gnu.org \
    --cc=wklew@mailbox.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).