GitLab

whether or not a step is actually computed is decided with logicals
(default all 3 steps are computed). This makes the implementation
of "solve_tridi" and "eigenvalues_only" a bit cleaner in the future

These can be used internally by

  call self%set_private(name, value)

   or

  call self%get_private(name, value)

but are not valid for the self%set()/get() routines, i.e. are not
visible to users of ELPA.

The public "solve" method has been renamed "eigenvectors" since it
computes the eigenvalues and (at least parts of) the eigenvectors

Another routine "eigenvalues" will just compute the eigenvalues

DATATTYPE instead of DATATYPE

This prevented builing for SUSE Leap_42.2 but actually this should
always have failed !

This is a bit cumbersome, as it involves yet another abstract
intermediate type, but necessary due to language limitations.

By mistake a procedure has been named
"invert_tridiagonal" but the correct name should be
"invert_triangular"

We decided not to provide this information via the key/value store, but
rather to use the ftimings module for that.

@loh will take care to implement ftimings in the new API
@amarek wants to port the legacy API so that the old global module
  variables still contain valid values

The legacy API is has been (internally) ported to use the new interface.
The intent is that users of the legacy API do not have to change their
codes.

Next step is to completely adapt the .gitlab-ci.yml file

Still missing is the compatibility layer, currently it only compiles
when configure is called with

  --disable-legacy

Also, a more general solution to parameter passing via environment
variables would be nice.