Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <4f6c9e17$0$1383$4fafbaef@reader2.news.tin.it>
References: <4f6c9e17$0$1383$4fafbaef@reader2.news.tin.it>
Date: Fri, 23 Mar 2012 12:33:35 -0400
Subject: Re: Stream programming
From: Nathan Rice <nathan.alexander.rice@gmail.com>
To: Kiuhnm <kiuhnm03.4t.yahoo.it@mail.python.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.934.1332520419.3037.python-list@python.org>
Lines: 65
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:22084

> I will use "<=3D>" to mean "is equivalent to". That's not part of the DSL=
.
> A flow has one or more streams:
> =A01 stream:
> =A0 =A0[1,2,3]
> =A02 streams:
> =A0 =A0[1,3,5] | [2,4,6]
> Two flows can be concatenated:
> =A0[1,2,3] + [4,5,6] <=3D> [1,2,3,4,5,6]
> =A0[0] + ([1,2] | [3,4]) + [10] <=3D> [0,1,2,10] | [0,3,4,10]
> =A0([1,2] | [10,20]) + ([3,4] | [30,40]) <=3D> [1,2,3,4] | [10,20,30,40]

Algebraically, your concatenation rules don't really make sense - your
flows are both distributive and non distributive.  You also make the
implicit assumption of an order over streams in a flow, but disregard
the implications of that assumption in some cases.  I understand what
you're trying to communicate, so I think you need to be a little more
strict and explicit in your definitions.

> A flow can be transformed:
> =A0[1,2] - f <=3D> [f(1),f(2)]
> =A0([1,2] | [3,4]) - f <=3D> [f(1,3),f(2,4)]
> =A0([1,2] | [3,4]) - [f] <=3D> [f(1),f(2)] | [f(3),f(4)]
> =A0([1,2] | [3,4]) - [f,g] <=3D> [f(1),f(2)] | [g(3),g(4)]
> =A0[1,2] - [f,g] <=3D> [f(1),f(2)] | [g(1),g(2)]

Given the examples you pose here, it is clear that you are assuming
that the streams are synchronized in discrete time.  Since you do not
provide any mechanism for temporal alignment of streams you are also
assuming every stream will have an element at every time point, the
streams start at the same time and are of the same length.  Is this
what you want?  These seem like pretty rough simplifying assumptions.

> Some functions are special and almost any function can be made special:
> =A0[1,2,3,4,5] - filter(isprime) <=3D> [2,3,5]
> =A0[[],(1,2),[3,4,5]] - flatten <=3D> [1,2,3,4,5]
> Note that 'filter' is not really necessary, thanks to 'flatten'.

This implies that your transformations again produce flows.  You
should explicitly state this.

> Flows can be named, remembered and used
> =A0as a value:
> =A0 =A0[1,2,3,4,5] - 'flow' + val('flow') <=3D> [1,2,3,4,5]*2

Is this a flow with two identical streams, or a flow with one long
stream formed by concatenation?

> =A0as a transformation chain:
> =A0 =A0[1,2,3] - skipfirst - 'again' | [4,5,6] - func('again')
> =A0 =A0 =A0<=3D> [2,3] | [5,6]
> =A0Recursion is also possible and stops when a function is applied to an =
empty
> sequence.
> Flows can be saved (push) and restored (pop) :
> =A0[1,2,3,4] - push - by(2) - 'double' - pop | val('double')
> =A0 =A0 =A0<=3D> [1,2,3,4] | [2,4,6,8]
> There are easier ways to achieve the same result, of course:
> =A0[1,2,3,4] - [id, by(2)]

You are grasping at an algebra here, a sort of calculus of temporal
observations.  You need to step back and make it rigorous before you
worry about issues such as a readable syntax.

Nathan