From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] I suppose if there's no other way to do it (a quote from the tcl web site)
Date: Fri, 11 Aug 2006 06:45:03 -0500 [thread overview]
Message-ID: <f2b6e3e0a9cbd3e5fb6822757bafd4b9@quanstro.net> (raw)
In-Reply-To: <3e1162e60608110021g6e820143oa2461d3d14b00103@mail.gmail.com>
*not* providing a library for these things is the key.
for example, page doesn't link against the jpeg library.
it just runs jpg. nedmail doesn't link against the mime
library, it uses upas/fs and marshal.
if plan 9 provided fancy library interfaces for such things,
we might be temted by the sirens "shared libraries" and "oop
languages".
- erik
On Fri Aug 11 02:22:13 CDT 2006, leimy2k@gmail.com wrote:
> On 8/10/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> > "Sure, some other languages have libraries for accessing web or ftp
> > sites, or looking inside zip files. But how many provide an open ended
> > and extensible system that allows you to access any such resource using
> > the same I/O commands you'd use with regular disk files?"
> >
>
> C++ iostreams perhaps? I've got one for sockets, pipes etc... Now
> that's not the same as FTP sites and zip files, but it could be done.
> Then you can use the same iterators and algorithms to glue it all
> together. In fact, I think I saw a zlibstream once. I was thinking
> of writing one.
>
> It's done via a blend of template generic programming and OOP. Too
> bad C++ quickly becomes quite confusing and is very easy to abuse and
> make difficult to maintain (probably an understatement).
>
> Plan 9 gives me a lot of that power right at the shell because the OS
> multiplexes 9P so well.
>
>
> > hmm. in the language library? Well, I guess if that's all you can do ...
> > but this is a really odd quote.
> >
> > And I actually like tcl ...
> >
> > ron
next prev parent reply other threads:[~2006-08-11 11:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 14:13 Ronald G Minnich
2006-08-11 0:26 ` LiteStar numnums
2006-08-11 7:21 ` David Leimbach
2006-08-11 11:45 ` erik quanstrom [this message]
2006-08-11 14:10 ` David Leimbach
2006-08-11 15:18 ` erik quanstrom
2006-08-11 14:16 ` Ronald G Minnich
2006-08-11 17:18 ` erik quanstrom
2006-08-12 6:19 ` Martin C. Atkins
2006-08-12 10:56 ` ems
2006-08-12 15:50 ` David Leimbach
2006-08-12 16:43 ` ems
2006-08-12 21:15 ` Paweł Lasek
2006-08-12 21:55 ` Russ Cox
2006-08-12 21:56 ` Russ Cox
2006-08-12 21:57 ` Francisco J Ballesteros
2006-08-13 3:25 ` Anthony Sorace
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=f2b6e3e0a9cbd3e5fb6822757bafd4b9@quanstro.net \
--to=quanstro@quanstro.net \
--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).