From: Quinn Dunkan <quinn@regurgitate.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Python filesystem
Date: Thu, 29 Nov 2001 21:44:51 -0800 [thread overview]
Message-ID: <20011130054456.04F068007B@regurgitate.ugcs.caltech.edu> (raw)
In-Reply-To: Your message of "Wed, 28 Nov 2001 18:18:02 GMT." <200111281818.fASII3T58143@devil.lucid>
> I know the answer to this mail should be :
>
> "send us the code when it's finished"
>
> but I've been musing the past couple of days about a python filesystem
>
> python is not just a script interpreter but it is also a kind of shell
Yes, most languages have REPLs.
> fire it up without a script and you can execute commands 'interactively'
>
> which means it's quite a candidate for a file system
>
> is it a technique that is used anywhere else?
plumber?
> the ability to embed a programming language that an application can send code
>
> to progressively sounds quite interesting
Isn't that just like creating a named pipe to a shell or REPL? Isn't that
what acme's win does?
A while back I wrote a lua program that served lua variables---a table becomes
a directory and strings become files, and functions became files containing
whatever string the function returns when passed nbytes read (bytes written
are passed as a string). And since most everything in lua is a table,
including the global namespace, you could assign variables by writing to
files. It presented a possibly interesting debugging interface, but not
practical. Type information is lost, because of table <-> directory and
everything else <-> bytes in file. And it's purely value-oriented, so as long
as you're treating data functionally you're fine, but if you want to alias you
can't.
But it's a fun way to throw up a filesystem fast (or interactively, by
assigning to the served table from the REPL).
next prev parent reply other threads:[~2001-11-30 5:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 18:18 Matt
2001-11-30 5:44 ` Quinn Dunkan [this message]
2001-11-28 18:21 Russ Cox
2001-11-28 18:34 ` Matt
2001-11-28 18:54 Russ Cox
2001-11-28 19:09 ` Matt
2001-11-28 21:46 ` Boyd Roberts
2001-11-29 12:24 ` Matt
2001-11-29 5:49 ` Lucio De Re
2001-11-29 6:30 ` Boyd Roberts
2001-11-29 6:31 ` George Michaelson
2001-11-29 7:10 ` Boyd Roberts
2001-11-29 11:26 ` Sam Holden
2001-12-06 16:56 ` Ralph Corderoy
2001-12-06 17:32 ` Boyd Roberts
2001-11-29 10:50 ` Lucio De Re
2001-11-29 11:06 ` Boyd Roberts
2001-12-06 15:59 ` Ralph Corderoy
2001-11-29 7:21 ` Skip Tavakkolian
2001-11-29 7:32 ` Steve Kilbane
2001-12-03 22:39 ` Laura Creighton
2001-12-07 9:36 ` Ralph Corderoy
2001-12-07 14:07 ` Laura Creighton
2001-11-29 7:37 ` Boyd Roberts
2001-11-29 11:10 ` Christopher Nielsen
2001-11-29 19:51 ` Skip Tavakkolian
2001-11-29 10:08 ` John Murdie
2001-11-29 10:37 ` Boyd Roberts
2001-11-29 12:03 ` Lucio De Re
2001-11-28 20:36 David Gordon Hogan
2001-11-29 10:23 rog
2001-11-29 10:54 ` Boyd Roberts
2001-11-29 14:49 Russ Cox
2001-11-29 19:28 ` Dan Cross
2001-11-29 20:02 ` Skip Tavakkolian
2001-11-29 20:05 ` Boyd Roberts
2001-11-29 20:01 Russ Cox
2001-11-29 20:37 ` Dan Cross
2001-11-29 20:49 ` Boyd Roberts
2001-11-30 16:01 ` plan9
2001-12-01 4:44 ` Boyd Roberts
2001-11-29 23:07 geoff
2001-11-29 23:26 ` George Michaelson
2001-11-30 0:11 geoff
2001-11-30 3:10 ` William Josephson
2001-12-08 19:58 Doug McIlroy
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=20011130054456.04F068007B@regurgitate.ugcs.caltech.edu \
--to=quinn@regurgitate.ugcs.caltech.edu \
--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).