Re: [eigen] Remove Eigen2 support for 3.2?

[ Thread Index | Date Index | More Archives ]

Is this a heavy maintainance burden or just a wish to simplify the codebase?

In the former case, go ahead and do whatever you need to keep Eigen
easy to maintain; in the latter case, I would suggest giving it a bit
more time and having a transition period where it would be officially
deprecated and complain loudly about it (generate warnings, or even
require people to #define
it in the version after (3.3?)

This is just my 2 cents as an industry guy now ;-) People just don't
want their existing code to be broken, and value that much higher than
"cleanliness" and "removing cruft".


2012/6/28 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
> Hi,
> unless there is any objections, I propose to remove the Eigen2 support
> code in the devel branch, i.e., for the future 3.2 release. I expect
> that all people already moved to Eigen3. The goal is to reduce the
> code base and simplify the implementation logic of some
> classes/functions.
> gael

Mail converted by MHonArc 2.6.19+