In order to reduce Shogun's complexity, it might be a good idea to drop the static interfaces (they have a long tail of tests, scripts, etc that make Shogun hard to overview). All but a single language are supported via the modular interfaces. The latter are way easier to maintain than the static ones for various reasons.
However, Shogun's Matlab support is only via static interfaces, and since SWIG does not support Matlab, we would loose the interface, which is unacceptable.
An even better approach might be to help the SWIG team to get Matlab support running. This would solve all our problems straight as Matlab would just be another language for Shogun. See
https://github.com/jaeandersson/swig/commits/matlab
In order to reduce Shogun's complexity, it might be a good idea to drop the static interfaces (they have a long tail of tests, scripts, etc that make Shogun hard to overview). All but a single language are supported via the modular interfaces. The latter are way easier to maintain than the static ones for various reasons.
However, Shogun's Matlab support is only via static interfaces, and since SWIG does not support Matlab, we would loose the interface, which is unacceptable.
Possible solutions:
Matlab via Java
It seems to be possible to call Java code from Matlab. Since we support Java modular, that might be a way. Somebody would have to prototype a single example. See for example http://www.mathworks.com/matlabcentral/answers/99993-how-do-i-call-a-simple-hello-world-java-program-in-matlab
SWIG and Matlab
An even better approach might be to help the SWIG team to get Matlab support running. This would solve all our problems straight as Matlab would just be another language for Shogun. See https://github.com/jaeandersson/swig/commits/matlab