MATLAB: Specify type of variable to allow tab completion

code analyzerMATLABmatlab coderobject-orientedoopstatic analysistab completiontype inference

Is there a way to indicate the type of a variable to the static analysis tool in Matlab to allow tab completion when coding?

This could be usefull when passing objects as an argument to a function.

Best Answer

Ken Atwell replied the question:

The new function argument validation allows to specify the type of function input variables. This will allow tab completion when writing the code.

This is new in Matlab 2019b and will cause syntax errors in any matlab version before 2019b.

More info here:

https://nl.mathworks.com/help/matlab/matlab_prog/function-argument-validation-1.html

Related Solutions

MATLAB: Autocomplete of properties for hgsetget derived class

I've been fiddling around and by mistake I found that the matlab.system.StringSet class of the matlab.System package allows exactly the < TAB > complete behaviour.

Note : the doc links are under symulink, however the package is under:

    fullfile(matlabroot, 'toolbox\matlab\system')

and therefore, does not require Symulink to be installed.

A barebone example :

classdef foo < matlab.System
    properties
        Coordinates
    end
    properties(Hidden,Transient)
        CoordinatesSet = matlab.system.StringSet({'north','south','east','west'});
    end
end

usage :

obj = foo
obj = 
  System: foo
    Properties:
      Coordinates: []
set(obj,'Coordinates','<TAB>

More details can be found on Limit property values to a finite set of strings

MATLAB: Passing on superclass property values to subclass

I think what Adam said here is the key:

but it knows it is creating this as part of creating the subclass

In other words, the 'obj' output of the myclass() constructor is not an ordinary output variable. Not only is it pre-initialized when the myclass workspace is entered, but the pre-initialization type also depends on how myclass() was invoked. If it was invoked using a subclass object, as in subclassObj@myclass() then obj is pre-intialized to the subclass type. This is confirmed by the following,

     classdef myclass 
         methods 
             function obj=myclass
                 disp ' '
                      disp(['obj is a ' class(obj) ' object'])
                 disp ' '
             end
         end
     end
    classdef mysubclass < myclass
        methods 
             function obj=mysubclass
                    obj=obj@myclass;
             end
         end
    end

which gives the behavior:

    >> myclass;
    obj is a myclass object
    >> mysubclass;
    obj is a mysubclass object

And therefore, assigning obj a superclass object, even in the superclass constructor, can force it to be the wrong type.

Best Answer

Related Solutions

MATLAB: Autocomplete of properties for hgsetget derived class

MATLAB: Passing on superclass property values to subclass

Related Question