unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: No Itisnt <theseaisinhere@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: GSOC applications coming up
Date: Tue, 30 Mar 2010 15:49:20 -0600	[thread overview]
Message-ID: <1e54fa2e1003301449h713d0805rd26a7402018146ee@mail.gmail.com> (raw)
In-Reply-To: <m3ljdbh305.fsf@pobox.com>

Hi, I don't think I can reply on the GSOC site, so I'll put it here

> Specifics on your proposal:
>
> * cothreads: Guile's partial continuations can implement this construct well, and correctly; while it's not necessary, it would be lots of fun. See "Prompts" in the manual.

I left it out because I have never used continuations. I'm confident I
will finish the entire standard library but the best laid plans of
mice and men and all that

>
> * repositories: I'd personally prefer to just have you commit to Guile's repository, in a branch, if you're happy with that.
>

It's all the same to me

> * test cases: Ideally you'd write something that uses Guile's internal (test-suite lib), adding lua.test to test-suite/tests/.
>

Yes

> * parser: how do you plan to implement this? I would use a lexer and an LALR parser. We will have an LALR parser generater documented and in core within the week.
>

Well I can tell you now I don't want to write it by hand. If my TDOP
parser bears out, I'll probably use that, otherwise I'll be looking
into parse-lalr etcetera. I'm also excited about PEG but it may not be
ready in time :)




      reply	other threads:[~2010-03-30 21:49 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
2010-03-30 21:49   ` No Itisnt [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=1e54fa2e1003301449h713d0805rd26a7402018146ee@mail.gmail.com \
    --to=theseaisinhere@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).