unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Andy Tai <atai@atai.org>, guile-user@gnu.org
Subject: Re: guile or scheme used to implement make or meson
Date: Wed, 13 Sep 2023 02:47:39 +0200	[thread overview]
Message-ID: <9584c56b-0e23-694e-d240-403aed12307e@telenet.be> (raw)
In-Reply-To: <CAJsg1E_453Bw6HKOif-OXkuDivjDEOxnPd-wkPU1ELDYi4Y5Kw@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 663 bytes --]

Op 11-09-2023 om 20:42 schreef Andy Tai:
> Is using Guile, or a similar Scheme implementation, to re-implement
> make or meson realistic?
> 

Meson seems to have straightforward syntax and semantics, and 
‘meson.build’ isn't actually Python code unlike what you might expect, 
so I think that a meson reimplementation using Guile is realistic.

Especially if you use python-on-guile (*), an implementation of Python 
in (Guile) Scheme, if you care more about interacting with or modifying 
Meson with Scheme than having an implementation written in Scheme.

(*) https://gitlab.com/python-on-guile/python-on-guile/

Best regards,
Maxime Devos

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2023-09-13  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 18:42 guile or scheme used to implement make or meson Andy Tai
     [not found] ` <2061904033.101273.1694496696500@mail.yahoo.com>
2023-09-12 12:39   ` Fw: " Mike Gran
2023-09-12 13:56 ` Olivier Dion
2023-09-12 14:10   ` Vivien Kraus
2023-09-12 15:20   ` Basile Starynkevitch
2023-09-12 16:04     ` Olivier Dion
2023-09-13  0:47 ` Maxime Devos [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=9584c56b-0e23-694e-d240-403aed12307e@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=atai@atai.org \
    --cc=guile-user@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).