Unset Variables
Default severity: Warning Auto-fix: No Category: Unset Variables Can be disabled: Yes Enabled by default: Yes
What this rule does
Detects variables that might not be defined before use. A single file-level engine (UnsetVariablesEngine) builds a symbol table and runs definite-assignment analysis to find variables used on code paths where they may never have been assigned. It covers 6 checks from MATLAB's "Unset Variables" category; each diagnostic carries the specific check ID (e.g. NODEF, PSET, STOUT).
Check IDs
NODEF
Severity: warning · Auto-fix: no
Variable might be used before it is defined.
USENS
Severity: warning · Auto-fix: no
Explicitly initialize this variable to avoid a potential uninitialized variable, or use a valid syntax for function call on line VAR_NUMBER.
PSET
Severity: warning · Auto-fix: no
Persistent variable is used, but might be unset.
SUSENS
Severity: warning · Auto-fix: no
Variable is used, but might be unset (within a script).
SVNODEF
Severity: warning · Auto-fix: no
Variable might not have a value, because variable definition may not be executed.
STOUT
Severity: warning · Auto-fix: no
Function return value might be unset.
Examples
Incorrect
function f()
disp(x); % NODEF: x may never be defined before use
end
function y = g()
if flag
y = 1;
end % STOUT: output not assigned on all paths
endCorrect
function f()
x = 0;
disp(x);
end
function y = g()
y = 0;
if flag
y = 1;
end
endConfiguration
[lint.rules.UNSET_VARIABLES_ENGINE]
severity = "warning"
ignore = ["myGlobalWorkspaceVar"]See Configuration for the full parameter list and rules.md for the complete rule inventory.