Comments on: Sharing Your M-Lint Settings http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/ Inside the MATLAB Desktop is written by the MATLAB Interface teams.<br /><br /><a href="http://blogs.mathworks.com/images/desktop/authors/team_small.jpg"><img src="http://blogs.mathworks.com/images/desktop/authors/team_tiny.jpg"></a> Fri, 29 Aug 2008 02:58:10 +0000 http://wordpress.org/?v=2.3.1 By: Ken http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3477 Ken Mon, 03 Mar 2008 18:49:40 +0000 http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3477 Thanks Quan. Collaboration is an oft overlooked portion of the work-flow. Thanks Quan. Collaboration is an oft overlooked portion of the work-flow.

]]> By: Quan http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3472 Quan Mon, 03 Mar 2008 16:45:48 +0000 http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3472 Great Post Ken. Writing code amongst many group members can cause many headaches from clashing styles and structure. Great Post Ken. Writing code amongst many group members can cause many headaches from clashing styles and structure.

]]> By: Ken http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3471 Ken Mon, 03 Mar 2008 14:40:37 +0000 http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3471 Hi Tim, Thats a great point - older M files were not written with the guiding hand of M-Lint. As an alternative to your suggestion, I'd recommend creating a second set of M-Lint settings and then switch to those settings when you open an older file. This certainly isn't as convenient and user-friendly as your method, but it would work in the interim. Thanks for the feedback Tim, -Ken Hi Tim,

Thats a great point - older M files were not written with the guiding hand of M-Lint. As an alternative to your suggestion, I’d recommend creating a second set of M-Lint settings and then switch to those settings when you open an older file.

This certainly isn’t as convenient and user-friendly as your method, but it would work in the interim.

Thanks for the feedback Tim,
-Ken

]]> By: Tim Davis http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3469 Tim Davis Mon, 03 Mar 2008 14:28:11 +0000 http://blogs.mathworks.com/desktop/2008/03/03/sharing-your-m-lint-settings/#comment-3469 I've noticed that M-lint can be harsh on M-files written for older versions of MATLAB. For example, take a look at Cleve Moler's NCM toolbox, or Nick Higham's matrix computation toolbox. There are lots of warnings such as "use two ampersands instead of one" in logical statements. These are both well-written codes, however. Here is a suggestion. What if an m-file could have a special help line that M-link recognizes (like "See also", "Copyright" etc). It could look like % Written for MATLAB Version 6.5 or something, which would tell M-lint not to complain about features used in MATLAB v6.5 that are no longer deemed acceptable. I write code that's meant to back-port to old versions of MATLAB, so I have to use lots of #%ok's to tell m-lint to keep quiet ... I’ve noticed that M-lint can be harsh on M-files written for older versions of MATLAB. For example, take a look at Cleve Moler’s NCM toolbox, or Nick Higham’s matrix computation toolbox. There are lots of warnings such as “use two ampersands instead of one” in logical statements. These are both well-written codes, however.

Here is a suggestion. What if an m-file could have a special help line that M-link recognizes (like “See also”, “Copyright” etc). It could look like

% Written for MATLAB Version 6.5

or something, which would tell M-lint not to complain about features used in MATLAB v6.5 that are no longer deemed acceptable.

I write code that’s meant to back-port to old versions of MATLAB, so I have to use lots of #%ok’s to tell m-lint to keep quiet …

]]>