Prev: Loading a very long excel file on a Mac platform
Next: guide de matlab
From: Yair Altman on 19 Jun 2010 17:29
"Steven Lord" <slord(a)mathworks.com> wrote in message <hvfu3l$cd0$1(a)fred.mathworks.com>...
>
> "Mason Freed" <mfreedREMOVETHIS(a)mfreedREMOVETHIS.com> wrote in message
> news:hve52s$1o9$1(a)fred.mathworks.com...
> > Any updates on this question?? There MUST be some way to distinguish
> > warnings from syntax errors using the mlint() function. The information is
> > obviously there - the editor shows them in different colors.
> >
> > Anybody?
>
> What do you intend to do with this information? Do you want simply to check
> if the function _can_ run without actually running it? Or do you want to
> get a list of errors so that you can tell someone specifically what
> lines/sections to fix?


In one of my applications I needed to enable the user to dynamically create executable Matlab code that would then be run interactively. This enabled users to create dynamic data analyses functions without actually needing to know Matlab or to code all the nuts-and-bolts of a regular Matlab function. For this I needed to display warnings and errors-on-the-fly and the OP's question goes directly to this need.

My solution was to use the undocumented internal function mlintmex, as follows:

errMsgs = mlintmex('-m2', srcFileName);
allMsgs = mlintmex('-m0', srcFileName);

numErrors = length(strfind(regexprep(errMsgs,'\*\*\*.*',''),char(10)));
numAllMsg = length(strfind(regexprep(allMsgs,'\*\*\*.*',''),char(10)));
numWarns = numAllMsg - numErrors;

(and from the messages themselves I extracted the actual error/warning location)

Yair Altman
http://UndocumentedMatlab.com
From: Mason Freed on 21 Jun 2010 11:23
First, thanks Yair. Your suggestion works perfectly, in a handful of lines. How do you find all of your nifty undocumented stuff?

Matt, thanks for the suggestion, which I think would work, but Yair's is much easier to implement.

And finally, Steven, the reason for my request is that I'm building an automated unit test system. It will run over all of our Matlab code whenever the source control system (subversion) registers a new commit. I want one of the policies to be that committed code contain no syntax errors. So I want a quick way to identify only the "killer" syntax errors. I can't make the policy that mlint reports no warnings at all, because the other developers would kill me for it. (Much as I would like to enforce that as a constraint.)

Thanks,
Mason
From: Yair Altman on 21 Jun 2010 12:17
"Mason Freed" wrote in message ...
> First, thanks Yair. Your suggestion works perfectly, in a handful of lines. How do you find all of your nifty undocumented stuff?

There are two main sources: reading/searching this newsgroup and reading the internal code of Matlab's m-files. I make a habit of noting down new stuff which is undocumented - then when the need occurs (often years later), I have an immediate answer.

Here's another thread that documents mlintmex usage that you may find useful, which I posted a few years ago: http://www.mathworks.com/matlabcentral/newsreader/view_thread/145245

In this particular case, I think I learned about mlintmex from the indomitable Us (Urs) Schwartz, but I can't find the original reference now. He also posted the related utilities FDEP and FARG on the File Exchange that you may find useful (as are all of his utilities). In any case, Us posted the following humorous comment about the source of *his* knowledge some years ago: http://www.mathworks.com/matlabcentral/newsreader/view_thread/115423#292260

Yair Altman
http://UndocumentedMatlab.com
From: Mason Freed on 21 Jun 2010 13:06
"Yair Altman" <altmanyDEL(a)gmailDEL.comDEL> wrote in message <hvo3ak$aeb$1(a)fred.mathworks.com>...
> "Mason Freed" wrote in message ...
> There are two main sources: reading/searching this newsgroup and reading the internal code of Matlab's m-files. I make a habit of noting down new stuff which is undocumented - then when the need occurs (often years later), I have an immediate answer.
>
> Here's another thread that documents mlintmex usage that you may find useful, which I posted a few years ago: http://www.mathworks.com/matlabcentral/newsreader/view_thread/145245
>
> In this particular case, I think I learned about mlintmex from the indomitable Us (Urs) Schwartz, but I can't find the original reference now. He also posted the related utilities FDEP and FARG on the File Exchange that you may find useful (as are all of his utilities). In any case, Us posted the following humorous comment about the source of *his* knowledge some years ago: http://www.mathworks.com/matlabcentral/newsreader/view_thread/115423#292260
>
> Yair Altman
> http://UndocumentedMatlab.com

Interesting - thanks for the references Yair.

One note that I found, related to both mlint and mlintmex: they seem to choke on files with spaces in the filename. These give back "Filename {strangely modified path here} is not formed from a valid MATLAB identifier." I'm writing a quick util to copy filenames containing spaces to a temp file and run mlintmex there, but do you have any other magic suggestions to tackle this issue?

Thanks,
Mason
From: Yair Altman on 21 Jun 2010 13:24
"Mason Freed" <mfreedREMOVETHIS(a)mfreedREMOVETHIS.com> wrote in message <hvo66e$gfu$1(a)fred.mathworks.com>...

> One note that I found, related to both mlint and mlintmex: they seem to choke on files with spaces in the filename. These give back "Filename {strangely modified path here} is not formed from a valid MATLAB identifier." I'm writing a quick util to copy filenames containing spaces to a temp file and run mlintmex there, but do you have any other magic suggestions to tackle this issue?


No magic suggestions for the simple reason that Matlab m-files should not have a space in their filenames... If you're doing check-in sanity checks as you wrote above then this would be one obvious source of reported error.

Yair Altman
http://UndocumentedMatlab.com
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Loading a very long excel file on a Mac platform
Next: guide de matlab