An intriguing problem. Personally I currently circumvent issues like this with the function below. That also allows me to trigger errors in carefully controlled places when running a tester function. I also tend to work with very small units of code, so it is easy to see where to add/remove mlint warnings.
function varargout=debug_hook(varargin)
%This function can be used to return several outputs (including warnings and errors), determined by
%the global variable HJW___test_suit___debug_hook_data.
%
%Every iteration the first element is removed from HJW___test_suit___debug_hook_data.
%
%When HJW___test_suit___debug_hook_data is empty or when returning a warning this functions returns
%the input unchanged.
global HJW___test_suit___debug_hook_data
if isempty(HJW___test_suit___debug_hook_data)
varargout=varargin;return
end
element=HJW___test_suit___debug_hook_data(1);
HJW___test_suit___debug_hook_data(1)=[];
switch element.action
case 'return'
varargout=element.data;
case 'warning'
varargout=varargin;
warning(element.data{:})
case 'error'
error(element.data{:})
case 'warning_'
varargout=varargin;
warning_(element.data{:})
case 'error_'
error_(element.data{:})
end
end
