From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: Re: [BUG] Eval sets incorrect runtime metainformation
Date: Sat, 6 Jul 2024 11:56:13 -0700 [thread overview]
Message-ID: <22db114f-5694-4cb0-a589-d06033c31fb3@gmail.com> (raw)
In-Reply-To: <718e88a7-36b8-4e72-84b6-5156f7d75896@philipmcgrath.com>
On 6/30/24 3:27 PM, Philip McGrath wrote:
>
> 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.
>
I've written a LALR parser generator (based on the algorithm in the
dragon book) and have produced
a few sample parsers and compilers. I always compile to tree-il. See
the javascript and mlang
subdirs under
https://git.savannah.nongnu.org/cgit/nyacc.git/tree/examples/nyacc/lang
Matt
next prev parent reply other threads:[~2024-07-06 18:56 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
2024-07-06 18:56 ` Matt Wette [this message]
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=22db114f-5694-4cb0-a589-d06033c31fb3@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@gnu.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).