MATLAB: Confusing m-lint behaviour after catch statement

Question

I notice in my own code (and in some professional code, eg. the database toolbox) that it's frequently convenient to use a try/catch block that doesn't make use of the resulting MException object.

For example, if I want to try some "dangerous" statement (say, writing to an database with an unknown connection) but am willing to "just go along" if it fails, I would write something like:

try
    cursor = exec(risky_connection, sql)
catch me %#ok
end

Given that m-lint complains about this by default, I presume there's a better construct to handle it… So what is it?

Answer 1

Hi,

the code analyzer has some dilemma here: the reason he tells you about the exception object is to make the programmer aware of using the object is much better then the previous lasterr constructs. I guess the optimal solution would be: complain about missing identifier ME only if the user uses lasterr or similar in the catch block, otherwise not. For now he just always complains...

Since you know about the exception objects, you might just turn off the warning in the preferences or do like cyclist does, just suppress ...

Titus