Your comments

Great!

Thank you very much for quick response ...!!!

Hi Pavel,


during last days I tried to clarify the above mentioned problem with "incompatibility" of your mex file on Matlab R2018a.


If I understand well information available here: https://www.advanpix.com/2013/07/19/undocumented-mex-api

you are using exactly this kind of undocumented functions and recent "incompatibilty" problem with R2018a could be caused by any change in these undocumented functions by TMW. Am I right?


In this case, is very important your statement:

"Please note that there is a risk in using the functions – MathWorks can

change / remove some of them in next versions. It is additional burden
for developer to stay tuned and update their toolboxes on time."


And moreover, undocumented function mxGetPropertyShared is called via C++ API (not via C API which is already exist for this function, but again as undocumented). This is already two serious reasons for potential problems! Direct calling via C interface is definitely more stable in every cases and scenarios.


I fully understand your main reason to choose these undocumented functions to get speed-efficient code. But on the other hand, you should definitely provide more thorough testing with latest Matlab version compatibility. 

Hi Pavel, you are right.

I just testing all my MEX files. TMW changed the MEX API so massively, that significant number of third-party MEX files I use (~20% in my case)  does not work with R2018a. This is terrible situation for all third-party matlab toolbox users!!!

I am a bit disappointed, how quietly is TMW  able to change the MEX API, without any warning to all third-party toolbox developers.