MATLAB Programming

MATLAB Path
If you then run the script, using run path/script, you will have created
the handles that you need.
For example,
1 Create a script in this off-path directory that constructs function handles
and assigns them to variables. That script might look something like this:
File E:/testdir/createFhandles.m
fhset = @setItems
fhsort = @sortItems
fhdel = @deleteItem
2 Run the script from your current directory to create the function handles:
run E:/testdir/createFhandles
3 You can now execute one of the functions by means of its handle.
fhset(item, value)
Making Toolbox File Changes Visible to MATLAB
Unlike functions in user-supplied directories, M-files (and MEX-files) in the
matlabroot/toolbox directories are not time-stamp checked, so MATLAB
does not automatically see changes to them. If you modify one of these
files, and then rerun it, you may find that the behavior does not reflect the
changes that you made. This is most likely because MATLAB is still using the
previously loaded version of the file.
To force MATLAB to reload a function from disk, you need to explicitly clear
the function from memory using clear functionname. Note that there are
rare cases where clear will not have the desired effect, (for example, if the
file is locked, or if it is a class constructor and objects of the given class exist
in memory).
Similarly, MATLAB does not automatically detect the presence of new files
in matlabroot/toolbox directories. If you add (or remove) files from these
directories, use rehash toolbox to force MATLAB to see your changes. Note
that if you use the MATLAB Editor to create files, these steps are unnecessary,
as the Editor automatically informs MATLAB of such changes.
12-37