From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d916d0fcaa1fcc6a1d22dc4cf445c654@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon,  6 Apr 2009 07:09:47 -0400
To: 9fans@9fans.net
In-Reply-To: <20090406035529.C9F5A5B21@mail.bitblocks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] typed sh (was: what features would you like in a shell?)
Topicbox-Message-UUID: d316c744-ead4-11e9-9d60-3106f5b1d025

> Nitpick: the output type of one command and the input type of
> the next command in the pipeline has to match, not every
> command.

i think this is wrong.  there's no requirement
that the programs participating in a pipeline are compatable
at all; that's the beauty of pipes.  you can do things
that were not envisioned at the time the programs were
written.

> To go beyond simple char streams, one can for example build a
> s-expr pipeline: a stream of self identifying objects of a
> few types (chars, numbers, symbols, lists, vectors). In Q
> (from kx.com) over an IPC connection you can send strings,
> vectors, dictionaries, tables, or arbitray Q expressions. But
> there the model is more of a client/server.

or ntfs where files are databases.  not sure if streams
can look the same way.

- erik