Re: [eigen] Future for Eigen 2.0

[ Thread Index | Date Index | More Archives ]

On Thu, Jan 16, 2014 at 4:57 PM, Christoph Hertzberg <chtz@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 16.01.2014 16:38, Benoit Jacob wrote:
What I don't know --- it is for current maintainers to tell --- is how much
maintainance cost is incurred by Eigen3's compatibility modes. If it were
significant, it could make sense to remove these modes from Eigen trunk and
communicate in the documentation that these modes are only available up to
version e.g. 3.2 and therefore people porting from Eigen 2 are invited to
first port to Eigen 3.2 before moving on to newer Eigen versions.

I think for pure maintenance the cost is neglectable. Problems might be bigger refactorings like the new _expression_ evaluation (but that's mostly a question Gael should answer).

yes, maintaining this compatibility layer after the _expression_ template refactoring will be a high cost, so for me it's pretty clear it has to be removed for 3.3.

If Eigen 2 documentation or other mentions on the website are confusing
visitors, then that's a real problem that needs to be solved, but perhaps
it could be solved by big red <blink> (oh wait, we just removed support
from that html tag...) warnings, while keeping Eigen 2 available for people
who still need it.

Do we have server logs how often dox-2.0/* is requested (by non-robots)?
Independent from that, I would support hiding it or marking it somehow as outdated (maybe change the style to orange letters on red background *g*).

we could prevent these pages to be indexed by robots, remove the 'Eigen 2' link from the sidebar, and replace the line:

'The last 2.0 (old series) release is Eigen 2.0.17. Get it here: tar.bz2tar.gzzipChangelog.'

by a link to a small Eigen2 page stating it's outdated with links to tarballs and doc.




Dipl.-Inf., Dipl.-Math. Christoph Hertzberg
Cartesium 0.049
Universität Bremen
Enrique-Schmidt-Straße 5
28359 Bremen

Tel: +49 (421) 218-64252

Mail converted by MHonArc 2.6.19+