I see, thank you for clarification.  MATLAB is huge, maybe something went wrong during update.

But definitely, this it is not a toolbox bug :).

I am not sure why this is happening.

But I suspect that freshly installed MATLAB might do some extra work in the background (building cache to speed-up startup time in future, or something similar). Do you see intensive processes in the background?

Hi Michal,

From the first glance conversion to mp is trivial for this script. 

Basically you only need to convert standard arrays to mp-type. 

So that just add 'mp' as last argument to every call to 'zeros', 'eye', etc. e.g.:

zeros(...) - > zeros(...,'mp')
eye(...) - > eye(...,'mp')
...

Also, of course, make sure input parameters to LinProg generate mp-values.

Let me know if you encounter any other issues.

Thank you for your help! We have just published a changelog for new version:

https://www.advanpix.com/documentation/version-history/

Thank you very much for doing the tests! This is very helpful for us.

@ I just solve the same incompatibility problem with TOMLAB toolbox and few other third-party commercial matlab toolboxes. 

Great! Do you have access to its source code or did you use some different approach?

New pre-release version of toolbox for GNU Linux is available for download.

Could you please download and test it with R2018a and older MATLAB(s) you have?

Thank you in advance, this would help us a lot.

Hi Michal,

Well, pre-release version of 2018a didn't have the issues. 

TMW introduced the changes only in the final release without any heads-up for toolbox developers (as they always do).

As for technical side - first of all, thank you for reading our blog :).

Changes in undocumented functions is just tip of the iceberg. In fact, fix is quite trivial for this issue alone.

TMW has also changed: (a) compilers they use for MATLAB, (b) the way they re-destribute CRT, (c) the way they re-distribute Windows API (on Windows they moved to universal CRT, which is compatible only with MSVC2015). These are what I referred to as "massive" changes/incompatibility.

We are working on making toolbox compatible with all these, without loss in speed.

But, still, this is also only part of the equation - unlike to TMW we must be backward compatible with previous versions of MATLAB. Almost every version of MATLAB has its own glitches in MEX interface and now we are including extra workarounds for R2018a.

In any case, updated version of toolbox for Windows is already available for download (was released in the morning).

GNU Linux & MacOSX versions will follow very shortly, if no new surprises will be found.  

Hi Michal,

R2018a has introduced massive changes in MEX API. 

(MEX API defines how third-party toolboxes interact with MATLAB's kernel. TMW has changed the API without any thought of backward compatibility and existing third-party toolboxes.)

We are investigating the situation in search for reliable workarounds. I hope to release update soon.

Please use R2017b for the moment.