Hi, > Does it time to consider Eigen 3.2 as stable too ? > > As I see portability is better [...] > Eigen is being successfully used with the following compilers [...]
Good, it seems to be fairly portable. I was surprised, last year (?), to learn that new compiler versions sometimes can't compile the code, but from the comments I received it seems that this is "normal" and happens for any advanced templated C++ code. It still seems strange to me, but I won't discuss C++ specifics. > Compilation and unit tests makes it as stable as possible. It looks good, but only if the unit tests are kept unchanged across successive versions (does Eigen 3.2 pass the unit tests of Eigen 3.0 and 3.1?). The underlying question is how long will code written for Eigen 3.2 be usable with the latest maintained version of Eigen. I'd like to see a statement like the one by GSL people[1] on the Eigen website. I'll ask specific questions about that on the eigen mailing-list, and bring this info here. [1] "GSL is a mature library with a stable API. The main emphasis is on ensuring the stability of the existing functions, tidying up and fixing any bugs that are reported." -- Nicolas LIMARE - CMLA - ENS Cachan http://limare.perso.math.cnrs.fr/ IPOL journal http://www.ipol.im/ -> image processing, reproducible research, open science
signature.asc
Description: Digital signature
-- IPOL - Image Processing On Line - http://ipol.im/ contact [email protected] - http://www.ipol.im/meta/contact/ news+feeds twitter @IPOL_journal - http://www.ipol.im/meta/feeds/ announces [email protected] - http://tools.ipol.im/mm/announce/ discussions [email protected] - http://tools.ipol.im/mm/discuss/
