Re: CONS specs update?

--===============1924943313==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5"
Content-Disposition: inline


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

> Just wondering if anyone has made any progress on the CONS spec? This
> thread has been silent for a while.

I'm on the structure of the new CONS system, but I was just too busy
last week to finish it.

In the meantime, If some people could write how a build must happen for
their favorite language, this would be great. I quickly installed a Wiki
for this purpose:

http://arcanes.fr.eu.org/~pierre/CONS%20revival/Wiki/index.cgi?SpecificBuil=
ds

No matter if many build descriptions are redundant, the main goal is to
have a broad view of what CONS will have to be able to do. The more
descriptions we have, the more chances we have to not forget something
important in CONS structure.

> I'd hate to see yet another effort to revive Cons drop flat.=20

Me too. ;-)

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

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

iD8DBQFA0J5Oxe13INnVDYoRAqG4AJ91u1joOVmRMB4m8nu6g3mErZzV6QCdH3+L
bfhytPNcx6Lk+MrcIjgZToU=
=Hh13
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--



--===============1924943313==
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/
--===============1924943313==--