From: Phil E <theseaisinhere@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Lua status update
Date: Tue, 17 Aug 2010 15:58:49 -0500 [thread overview]
Message-ID: <AANLkTik_nNzDML0t5PDK5djyD5E2YmJ2K494fk+2CiTh@mail.gmail.com> (raw)
I need to rewrite the parser (again), fix variable arguments, multiple
returns, and function environment handling, at which point I think it
will be suitable for inclusion in Guile. (Not that it'll be a drop-in
replacement for Lua, but at some point the only way I will be able to
improve it is through feedback) I'd also like to have some 5.2
compatibility, the rest of the standard library, and a wrapper around
the C runtime that allows Guile to use Lua C extensions. But with that
said, GSOC is over (which means if anyone reading this would like to
have a whack at any of this, be my guest), I'm happy with the results
and I hope we can get it included in Guile later on. Big thanks to
Andy and Ludo for putting up with me.
reply other threads:[~2010-08-17 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTik_nNzDML0t5PDK5djyD5E2YmJ2K494fk+2CiTh@mail.gmail.com \
--to=theseaisinhere@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).