9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Serving 9p in python - anyone started that?
Date: Thu, 14 Nov 2002 10:49:46 +0100	[thread overview]
Message-ID: <6ed5ff899befa6861e04b05c8e512751@plan9.escet.urjc.es> (raw)

> or data to an appropreate control or data files.   Yes, I agree.   However,
> rc is the one on which we do all those work?   I don't want to live with
> shell scripts even such rc.  Could we have more complete script
> language for this purpose?

When I wanted to be able to do 9p rc scripting, the tasks at hand were
simple.  For those times when it's not so simple I'd prefer to do that
in a language like limbo instead, and resort to C just when I need a
sharpen tool.

In fact, this summer I did a limbo to C translator, trying to get a
limbo version working natively in Plan 9.  My idea was to write also a
companion that could allow the translated limbo code to work with the
native libraries, so that the Alef history would not repeat (thrown
away because things had to be maintained twice, AFAIK).

Sadly, I was not happy at all with how it worked and I just did throw
it away.  Maybe next summer ;-)



             reply	other threads:[~2002-11-14  9:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  9:49 Fco.J.Ballesteros [this message]
2002-11-14 10:28 ` matt
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 20:56 markp
2002-11-14 21:02 ` matt
2002-11-14 18:54 Russ Cox
2002-11-15 11:52 ` Boyd Roberts
     [not found] <rsc@plan9.bell-labs.com>
2002-11-14 17:33 ` Russ Cox
2002-11-14 18:28   ` Scott Schwartz
2002-11-14 18:46     ` matt
2002-11-14 19:19       ` Dan Cross
2002-11-14 19:00     ` William Josephson
2002-11-14  9:42 okamoto
2002-11-14  8:53 Russ Cox
2002-11-14 17:05 ` Ronald G. Minnich
2002-11-14 18:24   ` Scott Schwartz
2002-11-14  8:34 Fco.J.Ballesteros
2002-11-14 17:37 ` John E. Barham
2002-11-13 19:18 Russ Cox
2002-11-13 17:22 matt
2002-11-13 19:33 ` John E. Barham

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=6ed5ff899befa6861e04b05c8e512751@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).