Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


Tree [r3612] /

File Date Author Commit
branch-4.000 2014-02-26 conrad_s [r3457] patch bump
branch-4.100 2014-03-17 conrad_s [r3503] document inv(diagmat(X))
branch-4.200 2014-04-08 conrad_s [r3509] yet another workaround for silly Intel compilers
branch-4.300 2014-06-24 conrad_s [r3577] backport fix
branch-4.320 5 days ago conrad_s [r3606] backport
branch-4.400 3 hours ago conrad_s [r3612] simplification
ext 2011-03-25 conrad_s [r1116] initial implementation of the 'mog_diag' class
notes 2014-01-08 conrad_s [r3329] move obsolete branches to old
old 2014-02-16 conrad_s [r3405] move branch-3.930 to old
papers 2013-02-28 eddelbuettel [r2450] with fixes
patches 2012-09-26 conrad_s [r2193] patch against branch-3.4, svn revision r2192: i...
README.txt 2013-08-24 conrad_s [r2789]

Read Me

This is the SVN repository for the Armadillo C++ linear algebra library.
For news and API documentation, see

Notes on SVN directory layout

The most recent "branch-x.y" folder contains new code, potentially unstable.

Once development has finished and the code has stabilised,
the branch is cloned under a new name, for new development.

For example, once branch-3.4 has stabilised, it is cloned as branch-3.6.
New development then takes place in branch-3.6.

Non-breaking API extensions are allowed within minor versions (eg. 3.4, 3.6, etc).
API breaks are disallowed between minor versions.
API stability is important, as Armadillo is used as a platform.

API breaks are only allowed between major versions (eg. going from 3.x to 4.0).
The breaks should be minor in scale -- users should not be burdened
with unnecessary or excessive API churn.
In other words, there has to be a good reason for an API change.

Folder "ext" contains unstable extensions