unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Martin Kuehl" <martin.kuehl@gmail.com>
Subject: Re: Status of the "Project Ideas" page / Summer of Code
Date: Sun, 30 Apr 2006 02:34:51 +0200	[thread overview]
Message-ID: <c1d5a43d0604291734u1a1bf6e8u41839aee9fddfd5a@mail.gmail.com> (raw)
In-Reply-To: <20060425141458.GG25279@gailuron.laas.fr>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Hello,

thanks for the helpful pointers; guile-debugging, guile-vm and the
compilation discussion all look quite interesting.  The hobbit topic
feels a little scary though, and I'm not sure I want to try that
before I've got a little more experience under my belt.

I was able to take guile-debugging for a spin, it's great, and I agree
that it makes more sense to complete it than to port swank (the lisp
server side of slime).  I'm not sure where one would start though --
the open bugs' summaries are maybe less descriptive than they might be
;)
[Hm.  Does it complete names of modules found on guile's load-path?]

Guile-VM also sounds neat, but I was neither able to compile the code
from CVS head nor to fetch the revival code from Ludovics arch repo,
which makes it even harder to devise a plan of action.  Judging from
the mail thread about its revival, completing the translation from
Scheme to Ghil and/or from Glil to assembly might be good candidates. 
Another might be comparison with "similar" VMs and ILs (the thread
mentions STklos; s48s "PreScheme" also comes to mind).

So... I'm willing to help -- is this roughly the right track?

Cheers,
 Martin

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel

  reply	other threads:[~2006-04-30  0:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 21:17 Status of the "Project Ideas" page / Summer of Code Martin Kuehl
2006-04-25 14:11 ` Andy Wingo
2006-04-25 22:56   ` Neil Jerram
2006-04-25 14:14 ` Ludovic Courtès
2006-04-30  0:34   ` Martin Kuehl [this message]
2006-05-02  8:39     ` Ludovic Courtès
2006-05-05 22:02       ` Martin Kuehl
2006-05-05 23:13         ` Clinton Ebadi
2006-05-04  9:40     ` Neil Jerram
2006-05-05 22:02       ` Martin Kuehl
2006-05-10 18:42         ` Neil Jerram
2006-04-30  7:38 ` Martin Kuehl

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=c1d5a43d0604291734u1a1bf6e8u41839aee9fddfd5a@mail.gmail.com \
    --to=martin.kuehl@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).