|Re: [eigen] eigen and API stability|
[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]
We are discussing the opportunity to add Eigen to this list of allowed
libraries. Eigen seems quite portable, as stated in the "Compiler
Support" section of the website main page. I see no statement about
the OS, so I suppose Eigen is OS-agnostic.
Is there a project policy regarding this API stability? Do you require
that any code written for Eigen 3.n is usable without changes with
Eigen 3.m for any m>=n? I understand there are some unit tests, but
are are all tests written for 3.n versions kept unchanged for future
What is the current development plan for Eigen, how long do you expect
to stay on the 3.x branch (which, I suppose, implies a major API version)?
And if/when Eigen moves to a 4.x branch, will the 3.x branch still be
maintained, especially fixed to be compilable with the latest compilers?
For example, I like this statement by GSL people: "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." If the same thing can not be written for Eigen
(or can it?), which API policy statement could be written instead?
All the best,
Nicolas LIMARE - CMLA - ENS Cachan http://limare.perso.math.cnrs.fr/
IPOL journal http://www.ipol.im/
-> image processing, reproducible research, open science
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|