coder.screener
Determine if function is suitable for code generation
Syntax
Description
coder.screener(
analyzes the entry-point
MATLAB® function fcn
)fcn
to identify unsupported functions and
language features as code generation compliance issues. The code generation compliance
issues are displayed in the readiness report.
If fcn
calls other functions directly or indirectly that are not
MathWorks® functions (MATLAB built-in functions and toolbox functions), coder.screener
analyzes these functions. It does not analyze the MathWorks functions.
It is possible that coder.screener
does not detect
all code generation issues. Under certain circumstances,
it is possible that coder.screener
reports false errors.
To avoid undetected code generation issues and false errors, before generating code, verify that your MATLAB code is suitable for code generation by performing these additional checks:
Before using
coder.screener
, fix issues that the Code Analyzer identifies.After using
coder.screener
, and before generating C/C++ code, verify that your MATLAB code is suitable for code generation by generating and verifying a MEX function.
The coder.screener
function does not report functions that the code
generator treats as extrinsic. Examples of such functions are plot
,
disp
, and figure
. See Use MATLAB Engine to Execute a Function Call in Generated Code.
coder.screener(
analyzes the
entry-point MATLAB function fcn
,'-gpu')fcn
to identify unsupported functions and
language features for GPU code generation.
coder.screener(
analyzes
multiple entry-point MATLAB functions.fcn_1,...,fcn_n
)
returns
a info
= coder.screener(___)coder.ScreenerInfo
object. The properties of this object contain the code
generation readiness analysis results. Use info
to access the code
generation readiness results programmatically. For a list of properties, see coder.ScreenerInfo Properties.
Examples
Input Arguments
Alternatives
Version History
Introduced in R2012b