9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "kazumi iwane" <kiwane@dream.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] RE: native limbo
Date: Sun,  6 May 2001 23:11:15 +0900	[thread overview]
Message-ID: <LPBBIBIIHKHEGDBPHBDOAEGPCAAA.kiwane@dream.com> (raw)
In-Reply-To: <200105011730.NAA24756@augusta.math.psu.edu>

> From: Dan Cross
> In article <LPBBIBIIHKHEGDBPHBDOKEGFCAAA.kiwane@dream.com> you write:
> >2) a dis interpreter and plan9 native modules
> >
> >Similar to 1), but modules and apps in dis binary. Thanks to Vita Nuova,
> >there already is a limbo-to-dis compiler on plan9 (right? don't know how
> >inferno/emu-dependent it is, though). You'd invoke a dis interpreter,
> >which would provide gc, syscall i/f and whatnot, to execute limbo apps.
>
> Hmm, not to be contrary, but isn't this basically what emu does
> already?  It provides a dis interpreter, plus modules which map native
> limbo services into native Plan 9 services (eg, a call to Sys->open()
> gets mapped into open(2)).  Maybe I'm missing something.

In this scenario, I dreamed of having modules that closely match plan9
native system calls, device drivers interface and namespace conventions,
but not necessarily those of inferno. Significant overlap, sure. Gratuitous
incompatibilities, maybe. In areas where inferno is ahead, notably Tk, I'd
steal them and adopt them to plan9 native services :-).

Also, a dis interpreter should be a plan9 native executable, so that limbo
apps would be just like C apps but interpreted; a web browser written in
limbo would run directly in a rio window, you could write a plan9 user level
file server in limbo, etc..

I gues I'm on the "yet another language" camp.

- kazumi




      reply	other threads:[~2001-05-06 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01 16:04 [9fans] " kazumi iwane
2001-05-01 17:30 ` Dan Cross
2001-05-06 14:11   ` kazumi iwane [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=LPBBIBIIHKHEGDBPHBDOAEGPCAAA.kiwane@dream.com \
    --to=kiwane@dream.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).