Re: GePhex 0.5: why guile?

Martin Bayer <[email protected]> Wed, 15 Feb 2006 00:36:49 +0100
Newsgroups gmane.comp.video.gephex.devel
Message-ID <[email protected]>
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1998896074==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig47973015EA68B7C90243EAB3"

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

Hi JS,

> But I guess we all start to see the limitations and implications of that
> approach. But if the core is programmed in C++ anyway, why the need for
> a scripting layer?

Scheme is a good base for domain specific languages. And we need a dsl
that describes the structure of complex dataflow systems. The generated
dataflow graphs are just simple scheme data structures and can be the
building blocks from new more complex graphs. With a script language it
is simple to write complex test cases like: Generate random filter
chains  with 5-20 filters...

Martin

--------------enig47973015EA68B7C90243EAB3
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)

iD8DBQFD8mmYCm3i57PRsbsRAj5nAJ9RQJpbxtAjef5lfsejYr3e1/WrmgCcD8Lv
Z5puUJILJFLFwBIN9vFS+V0=
=WrN/
-----END PGP SIGNATURE-----

--------------enig47973015EA68B7C90243EAB3--

--===============1998896074==
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

--===============1998896074==--