Re: GePhex 0.5: why guile?

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

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

Hi JS

>    The Drone team is currently considering using a script layer under
> the GUI.

That's a good idea :)

 I've noticed that you guys have opted for guile + home bytecode
> solution. I wonder why you have done that instead of using mzScheme,
> which already have a bytecode compiler.

Our first experiments with scheme and gephex where done with mzscheme.
Something like a bytecode compiler is in my opinion not very important
for our use, because the scheme layer is on top of the realtime layer
written in c++. And the design of the communication protocol between
them must ensure that the realtime system can't be blocked by the scheme
layer.

Martin

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

iD8DBQFD8l5qCm3i57PRsbsRAix9AJ0QlQazXXX6QgvZwjsyLiYpRzvt/QCeMEj5
TaEAZpzaEk1kp1AQFv1U2Xc=
=k7H5
-----END PGP SIGNATURE-----

--------------enig97D102F35F1471D8F10B28D4--

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

--===============1714791813==--