Re: Split cons code (was: Re: Debian package and development of CONS)

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


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

> - redundant code wrt CPAN (e.g. option handling)

In fact, in the Debian package I'm creating with 2.3.0, I just removed
all CPAN modules, and used packages dependency. I think we must not
continue including CPAN modules in the code, before it would be up to us
to check bug fixes for this code...

> - huge learning curve to understand cons internals.

I'm facing it! :-/

If someone can help me doing an first try splitting Cons, I would be
happy...

For the following development, I was thinking of modules adapted to
languages:

Cons::Compilation (C/C++/Objective-C/Java/Fortran/ASM/etc.)
Cons::Tex
Cons::SGML (and XML)

I would want to group everything that obey a similar construction
process.

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

--rPH0Y77Oimr1cvNq
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/V0k2xe13INnVDYoRAuNbAJ0XDIW7SmCvhnK53umen6FpJb3GfQCfcib0
SSmLmv8f9f+DmrtueYD+nXw=
=v9oG
-----END PGP SIGNATURE-----

--rPH0Y77Oimr1cvNq--



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

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