From: Andy Wingo <wingo@pobox.com>
To: No Itisnt <theseaisinhere@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: GSOC applications coming up
Date: Mon, 29 Mar 2010 11:48:58 +0200 [thread overview]
Message-ID: <m3ljdbh305.fsf@pobox.com> (raw)
In-Reply-To: <1e54fa2e1003281517s4015dfdei5964b209c2eb69b9@mail.gmail.com> (No Itisnt's message of "Sun, 28 Mar 2010 16:17:20 -0600")
Heya,
On Mon 29 Mar 2010 00:17, No Itisnt <theseaisinhere@gmail.com> writes:
> At the moment I'm tinkering with the arithmetic parser I posted to
> guile-user, and trying to turn it into a parser generator.
Cool!
> I expressed some interest in doing GSOC with Guile a little earlier
> and if y'all are willing to back me up, I really should write a
> proposal and submit it (I guess I'd just submit it to the GNU Project,
> assuming you approve?)
Sure, that would be fantastic.
> I'm still plenty open to suggestions; I'm particularly interested in
> parsing and compilation, but mostly I just want to write some Scheme.
How about that Lua implementation you proposed? I don't think there's
enough left on the Javascript compiler for it to be a summer project,
but poking around in that code could be instructive to see how it all
breaks down between the parser/compiler and the GOOPS-based runtime.
> What exactly needs to be finished in the Javascript compiler?
The standard library, mainly. I left it in a poor state, unfortunately,
without test cases, and without a TODO list; I am a bad person :P
> Let me know what you think.
I think it's going to be a lovely summer :) Speaking from experience,
writing compilers and runtimes is really, really educational, and
often the results are practically useful. It would be great to be able
to extend Emacs in Lua.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-03-29 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 22:17 GSOC applications coming up No Itisnt
2010-03-29 9:48 ` Andy Wingo [this message]
2010-03-30 21:49 ` No Itisnt
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=m3ljdbh305.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=theseaisinhere@gmail.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).