Why are some functions listed as not compatible with MATLAB Compiler, when they are in fact used and compilable in the Simulink Standard Library?

For example,

set_param

is listed as not compatible with MATLAB Compiler (see here: https://fr.mathworks.com/help/compiler/unsupported-functions.html)

But it is used in the initialization mask of the Saturation Dynamic block, which is compatible with Simulink Compiler (successfully tested on my end).

How come?

My hypothesis is that the banned function is used during the initialization phase, therefore can be fully resolved during the compilation, and is not used during the runtime. Is that correct?

Thank you.

Answer 1

[Steven Lord]

Some functions and functionality is supported with MATLAB Compiler but not Simulink Compiler.

Some functions and functionality is supported with Simulink Compiler but not MATLAB Compiler.

Some functions and functionality is supported with neither MATLAB Compiler nor Simulink Compiler.

See this page for a summary of what is supported by each product.

[Pierre-Augustin]

I see, thank you. That would mean that the aforementioned function set_param is not compatible with MATLAB Compiler but can be compatible with Simulink Compiler - the documentation indicating which blocks are compatible.