Can i use Matlab OOP and still use Compiler SDK

I want to redo all my algorithm code to Matlab OOP. Currently my code has a single entry point from the commercial application and it is compiled into a .NET assembly. If I maintain the same Matlab interface to the calling program can I change all the underlying code to Matlab OOP without messing anything up?

Answer 1

[Walter Roberson]

https://www.mathworks.com/products/compiler/supported/compiler_support.html

"MATLAB Compiler supports the full MATLAB language including objects, most MATLAB toolboxes, and user-developed user interfaces."

https://www.mathworks.com/products/matlab-compiler-sdk.html

"MATLAB Compiler SDK™ extends the functionality of MATLAB Compiler™ to let you build C/C++ shared libraries, Microsoft® .NET assemblies, Java® classes, and Python® packages from MATLAB® programs. These components can be integrated with custom applications and then deployed to desktop, web, and enterprise systems."

So, yes, you should be fine with Compiler SDK as long as you do not use one of the functions that cannot be compiled anyhow.

[Eugene Davis]

Thanks Walter. A followup if you please. Should I wrap the Matlab OOP program in a standard Matlab function. Then I assume what I've done moving from Matlab procedural programs that have a bunch of .m function to a bunch of .m class def files will be invisible to the calling program. I assume the Compiler SDK will know how to make sure all the class def files are included as it knew what .m function files to include when building the .NET assembly.

[Walter Roberson]

My understanding is that the constructor need to be called from a regular function for the purpose of compilation.

It should pick up all the needed files from the @ directories on the MATLAB path.