From: Rob Browning <rlb@defaultvalue.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: [BUG] Eval sets incorrect runtime metainformation
Date: Sat, 06 Jul 2024 11:42:49 -0500 [thread overview]
Message-ID: <87frsmqxo6.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <718e88a7-36b8-4e72-84b6-5156f7d75896@philipmcgrath.com>
Philip McGrath <philip@philipmcgrath.com> writes:
> I hadn't realized that other languages in Guile might compile to Tree-IL
> directly instead of generating syntax objects. Is that common and/or
> encouraged? It seems like it would require the new language's compiler
> to do a lot of work that could otherwise be delegated to Guile, and it
> would make it difficult to implement parts of the new language using macros.
For what it's worth, Lokke (a Clojure dialect) does both. For the most
part it compiles by producing Scheme code from its reader that's then
rewritten by macros. But it also includes a pass or two at the Tree-IL
level to handle some things that would be difficult to get right
otherwise (while also preserving the fairly tight integration with
Scheme that's intended).
For example, they handle adding support for "keywords as functions" (in
a generalized way), and resolving Clojure's namespaced symbols to Guile
module refs.
For anyone interested in the current arrangement (the README also covers
a bunch of limitations, differences, etc.):
https://codeberg.org/lokke/lokke/src/branch/main/DESIGN.md
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2024-07-06 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 15:07 [BUG] Eval sets incorrect runtime metainformation Andrew Tropin
2024-06-26 9:24 ` Andy Wingo
2024-06-26 9:36 ` Maxime Devos
2024-06-26 11:41 ` Andrew Tropin
2024-06-26 22:06 ` Philip McGrath
2024-06-28 13:20 ` Andrew Tropin
2024-06-29 19:55 ` Philip McGrath
2024-06-29 23:05 ` Maxime Devos
2024-06-30 22:27 ` Philip McGrath
2024-07-01 9:06 ` Maxime Devos
2024-07-06 16:42 ` Rob Browning [this message]
2024-07-06 18:56 ` Matt Wette
2024-06-26 16:04 ` Andy Wingo
2024-06-28 13:27 ` Andrew Tropin
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=87frsmqxo6.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=philip@philipmcgrath.com \
/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).