On Mon, Aug 11, 2008 at 05:38:46PM +0200, Burcin Erocal wrote:
1. does Ginac (or the part we plan to use) have *any* known bugs at all?
Yes, although it's purely theoretical: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479163
2. does Ginac have a test suite?
Yes, have a look at the check directory.
3. does ginac have a bug tracker?
No.
4. what does Valgrind say about the quality of the code when run on the test suite? memory leaks?
Valgrind reports the memory allocated for static objects as a leak. AFAIK valgrind does so for any C++ library which has static objects (with non-trivial constructors and destructors), so this might be a misfeature of valgrind. Still I'm not quite sure, this might be also an actual bug. Any ideas on debugging this are wellcome. I routinely use GiNaC in long-running computations, so the *actual* memory leaks get noticed and fixed (see e.g. commit dcb1d9061e4ce0a012d145530384541fc941fef4). Best regards, Alexei -- All science is either physics or stamp collecting.