3.0 won't have great developer documentation as we need it released ASAP, let's not miss the train on 3.1. This depends on a few deep internal changes needed for 3.1, which would make obsolete parts of developer docs written until now.
sadly we missed it :(
Is there a rush in releasing 3.1 at the moment? And more importantly, has anyone even remotely started thinking about working on this issue? Otherwise, I can almost guarantee that you will miss it again for 3.2 :( Over the years I'm using Eigen, I more-or-less find most things in the Eigen code with reasonable effort, but I'm afraid that I'm too far from being able to document it (especially, I don't understand every internal design decision, etc). Furthermore, solving bug 339 (self contained headers) would make things much easier already. This would not be much effort (and could easily be done before releasing 3.1), though it could raise many conflicts if done non-coordinated.
Also, installing a DXR instance would considerably help navigating the source tree! See e.g. http://dxr.lanedo.com/
(In reply to comment #2) > And more importantly, has anyone even remotely started thinking about working > on this issue? Otherwise, I can almost guarantee that you will miss it again > for 3.2 :( The plan is (or at least it was a year ago) to finish the work on evaluators (bug 99) first and then write developer documentation. The idea is that it would not make sense to write docs that will be soon out of date; evaluators represent a fairly drastic re-design of the Eigen core. Unfortunately, a year later we found that not a lot of progress has been made on evaluators.
(In reply to comment #4) > The plan is (or at least it was a year ago) to finish the work on evaluators > (bug 99) first and then write developer documentation. The idea is that it > would not make sense to write docs that will be soon out of date; evaluators > represent a fairly drastic re-design of the Eigen core. > > Unfortunately, a year later we found that not a lot of progress has been made > on evaluators. ok, fair enough. Still it would be a first step to solve bug 339 (and install a DXR for people who like it -- I myself prefer not switching between browser and IDE for developing). And actually, the same question remains w.r.t. bug 99, is there somebody actively working on it? And is there some documentation about evaluators somewhere besides in the corresponding BZ thread (either as they are now or they intend to be)? That would be helpful if you want others to contribute to that task.
I increased the importance to "normal" (although it actually could be even higher) and added some more dependencies.
I added a EIGEN_INTERNAL_DOCUMENTATION flag to build the \internal parts of the documentation (without manually changing the generated Doxyfile): https://bitbucket.org/eigen/eigen/commits/090787aa84 We could set even more flags in the Doxyfile if that option is enabled, and maybe we could automatically build and upload that (though it's not really of public interest)
-- GitLab Migration Automatic Message -- This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/138.