Re: Gephex 0.5: about the control flow

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1838536138==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig4C0C5A4452651FE677C05D61"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4C0C5A4452651FE677C05D61
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> So ... how do you deal with multiple sink? Like, say, suppose I have the
> following graph:
> 
> source --> goo --> sink1
>            |
>            -----> sink2
> 
> Clearly, the following would not work:
> 
> (sink1 (goo (source)))
> (sink2 (goo (source)))
> 
> since how then would you differentiate it from the graph:
> 
> source --> goo --> sink1
> source --> goo --> sink2

perhaps something like:

(define result (goo (source)))

(sink1 result)
(sink2 result)

But there are still a lot of questions about the syntax and semantic of
the domain specific language.

Martin

--------------enig4C0C5A4452651FE677C05D61
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD8mw4Cm3i57PRsbsRAvZjAJ0d7JRt0o30gMM9pGrSwqiCgVSoJgCeJ7S+
XjBtDRLOgPrKmIU6knKQEm8=
=vqNt
-----END PGP SIGNATURE-----

--------------enig4C0C5A4452651FE677C05D61--

--===============1838536138==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel

--===============1838536138==--