unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: on bootstrapping: first Mes 0.3 released
Date: Sun, 25 Dec 2016 16:11:39 +0100	[thread overview]
Message-ID: <87oa00cac4.fsf@gnu.org> (raw)
In-Reply-To: <87mvfr3m90.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 19 Dec 2016 17:40:59 +0100")

Ludovic Courtès writes:

Hi!

> Impressive!

Thanks!

> Is it a goal to try interpret a language as close as possible to that of
> Guile, and have the same libraries?  I guess that could help in the
> future: we could use (system base lalr), nyacc, etc.

We definitely want Nyacc and PEG, and who can live without lambda*?
Other than that I intend to cut as many corners as I can get away with,
also wrt Guile compatibility; at least for now.

> Also, currently there’s approximately 2K lines of C.  How do you plan to
> make sure that it doesn’t grow over time, or even that it shrinks?  :-)

It was worse, about 2600LOC.  I worked very hard last week and also had
a bit of luck.  I found a performance clue-bat while reading Guile-1.8's
eval.c; now macros are expanded only once.

This helped so much that I finally started moving stuff from the C
prototype into Scheme; about 1000LOC have been removed.  The intepreter
with all dependencies, including cell creation and garbage collector is
now ~1000LOC.  That is able to execute a Scheme program that has been
loaded into memory.  Another ~500LOC is spent to load a minimal Scheme
program and to dump it, to provide a small posix interface, math
functions and do some error reporting.

Next up: 0.4 release.  Then I want to start working on the now very
simplistic compiler backend and hook it up to Nyacc's AST.  As the
current proof-of-concept C compiler runs in Guile too and Nyacc runs
in Mes this can be all done in Guile or a joint Guile/Mes project.

> This all sounds very promising, thanks a lot!

Yay, quit happy to hack on this!

Greetings,
Jan

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  



      reply	other threads:[~2016-12-25 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 21:10 on bootstrapping: first Mes 0.3 released Jan Nieuwenhuizen
2016-12-12 22:17 ` Arne Babenhauserheide
2016-12-12 22:27   ` Jan Nieuwenhuizen
2016-12-13 22:43     ` Arne Babenhauserheide
2016-12-16 16:21     ` Christopher Allan Webber
2016-12-20  7:58       ` Jan Nieuwenhuizen
2016-12-19 16:40 ` Ludovic Courtès
2016-12-25 15:11   ` Jan Nieuwenhuizen [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=87oa00cac4.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).