unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ian Price <ianprice90@googlemail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: guile-user@gnu.org
Subject: Re: any thoughts on guile as a kernel extension language
Date: Fri, 27 Jan 2012 22:22:59 +0000	[thread overview]
Message-ID: <87k44cyed8.fsf@Kagami.home> (raw)
In-Reply-To: <87d3aee516.fsf@gmx.com> (Eric Schulte's message of "Fri, 20 Jan 2012 09:02:13 -0700")


Eric Schulte <eric.schulte@gmx.com> writes:

> The following immediately made me think of guile.
> http://netbsd-soc.sourceforge.net/projects/luakern/

It's long since dead, and Linux rather than Hurd, but
http://abstractnonsense.com/schemix/ is somewhat relevant.

-- 
Ian Price

"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"



      parent reply	other threads:[~2012-01-27 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 16:02 any thoughts on guile as a kernel extension language Eric Schulte
2012-01-20 19:36 ` Daniel Ridge
2012-01-20 22:12 ` Ludovic Courtès
2012-01-27 22:22 ` Ian Price [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=87k44cyed8.fsf@Kagami.home \
    --to=ianprice90@googlemail.com \
    --cc=eric.schulte@gmx.com \
    --cc=guile-user@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).