Hello! CLN is a great library, but it has a number of problems. 1. CLN can be built only with GNU C++ compiler. Even worse -- some bits of CLN (in particular, include/cln/modules.h) work only with specific versions of GCC, so CLN can break at any moment (this actually happens with every new [major] release of GCC). 2. The code is a bit obfuscated. 3. The build scripts are extremely user- and hacker-hostile. Since CLN developers keep [silently] refusing patches addressing these issues, I've decided to fork CLN. The code can be obtained from git repository: git://ffmssmsc.jinr.ru:443/varg/cln.git To view the repository on-line point your browser to http://ffmssmsc.jinr.ru/~varg/git/gitweb.cgi?p=varg/cln.git Best regards, Alexei -- All science is either physics or stamp collecting.
Alexei Sheplyakov wrote: <snip>
Since CLN developers keep [silently] refusing patches addressing these issues, I've decided to fork CLN. The code can be obtained from git repository: </snip>
Does (and will) GiNaC bother about what implementation of CLN is built onto? Cheers, p.
Hi, On Wed, Aug 27, 2008 at 02:49:27PM +0200, Pierangelo Masarati wrote:
Does (and will) GiNaC bother about what implementation of CLN is built onto?
All programs which work with original version of CLN should work with modified one, anything else is a bug. Unfortunately my modifications break the binary compatibility, so recompilation is required. Best regards, Alexei -- All science is either physics or stamp collecting.
participants (2)
-
Alexei Sheplyakov
-
Pierangelo Masarati