Confusing m-lint behaviour after catch statement
显示 更早的评论
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?
采纳的回答
Titus Edelhofer
2011-12-7
0 个投票
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
更多回答（1 个）
the cyclist
2011-12-7
0 个投票
Have you read the detailed description of that particular m-lint warning? In a nutshell, it just says that best practice to use the exception identifier in the catch statement, etc.
Personally, I generally just suppress that m-lint warning. :-)
类别
在 帮助中心 和 File Exchange 中查找有关 Matrix Indexing 的更多信息
产品
2011-12-7
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
Translated by 
