In R2010b, I find that the Dependency Analyzer gives me warnings about not being able to find various routines; the routines it reports are subfunctions whose handle I am taking. For example,
uicontrol(...., 'Callback', @MyCallback)
then if MyCallback is a subfunction in the same file, the analyzer reports it as not found.
I checked the documentation for function_handle, which says
"At the time you create a function handle, the function you specify must be on the MATLAB path and in the current scope of the code creating the handle. For example, you can create a handle to a subfunction as long as you do so from within the file that defines that subfunction."
This seems to specifically allow the construct that the analyzer is having problems with.
R2008b's Dependency Analyzer correctly reports the routines as subfunctions.
Is this just a bug in R2010b's Dependency Analyzer, or is there a change in functionality at stake?
interesting observation. It persists in R2012a. On first glance I would agree this should be caught by dependency analysis. I will contact our development to see what's going on.
The report does not list:
Files called from eval, evalc, run, load, function handles, and callbacks. MATLAB does not resolve these files until run time, and therefore the Dependency Report cannot discover them.