From: Timothy Sample <samplet@ngyro.com>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: guile-user@gnu.org
Subject: Re: Inconsistencies with free-identifier=? and bound-identifier=?
Date: Fri, 28 Jul 2023 22:37:51 -0600 [thread overview]
Message-ID: <87wmyjgwo0.fsf@ngyro.com> (raw)
In-Reply-To: <6195a14f3877dff0b8dfc2a5d1d35e89b3d4f144.camel@abou-samra.fr> (Jean Abou Samra's message of "Fri, 28 Jul 2023 12:09:43 +0200")
Jean Abou Samra <jean@abou-samra.fr> writes:
> Le jeudi 27 juillet 2023 à 12:28 -0600, Timothy Sample a écrit :
>
> May I ask why you are exploring this? It’s quite arcane!
>
> Because I am writing my own syntax expander :-)
Nice! Best of luck to you. :)
> (This is a school project, nothing serious. Still, formalizing the
> macro system is kind of the whole point. I wanted to make sure I was
> getting it right, but now I'm discovering that "right" is not a thing
> here :-).
>
> Thanks for your links, I will read them.
One other one that I will point out is “Inferring scope through
syntactic sugar” by Justin Pombrio, Shriram Krishnamurthi, and Mitchell
Wand (https://dl.acm.org/doi/10.1145/3110288). I didn’t get a ton out
of it (maybe I didn’t understand it!), but since you mentioned
formalizing, they give a more formal definition of variable scope
(section 3) that might interest you.
-- Tim
prev parent reply other threads:[~2023-07-29 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 0:20 Inconsistencies with free-identifier=? and bound-identifier=? Jean Abou Samra
2023-07-21 9:08 ` Jean Abou Samra
2023-07-27 18:28 ` Timothy Sample
2023-07-27 22:10 ` Timothy Sample
2023-07-28 10:08 ` Jean Abou Samra
2023-07-28 10:09 ` Jean Abou Samra
2023-07-29 4:37 ` Timothy Sample [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=87wmyjgwo0.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guile-user@gnu.org \
--cc=jean@abou-samra.fr \
/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).