Re: Request for comments: CONS specification

--===============0033829511==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="p6hDAtPN9q+ZnUca"
Content-Disposition: inline


--p6hDAtPN9q+ZnUca
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> If we can reuse existing code, there's no need to reinvent the wheel.

Yes, but it will have to follow the specifications by 100%.

And if some parts of Cons are specified very precisely, writing the
corresponding code will be straightforward. If we could achieve
specifying alebrically some parts, these ones could nearly be written
automatically...

Quickly,
le Moine Fou
--=20
[email protected]
OpenPGP 0xD9D50D8A

--p6hDAtPN9q+ZnUca
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFAu7Ywxe13INnVDYoRAu1PAKCQ/vz2sN/vXJa8VmYibIcgKeHisgCgh4Jp
5ObyBxVtI/ybYMZDTC7FIow=
=78Of
-----END PGP SIGNATURE-----

--p6hDAtPN9q+ZnUca--



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

_______________________________________________
[email protected]
http://lists.gnu.org/mailman/listinfo/cons-discuss
Cons URL: http://www.dsmit.com/cons/
--===============0033829511==--