From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: check syntax errors in m file
Date: Tue, 22 Jun 2010 15:38:22 +0000 (UTC)
Organization: The MathWorks, Inc.
Lines: 20
Message-ID: <hvqlde$4bp$>
References: <h37tdl$gpd$> <hve52s$1o9$> <hvfu3l$cd0$> <hvjcr0$j79$> <hvo059$fcq$> <hvod1p$855$> <hvoirg$g9e$> <3n_Tn.2420$Yo5.136@newsfe01.iad>
Reply-To: <HIDDEN>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: 1277221102 4473 (22 Jun 2010 15:38:22 GMT)
NNTP-Posting-Date: Tue, 22 Jun 2010 15:38:22 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 2305417
Xref: comp.soft-sys.matlab:647069

Walter Roberson <> wrote in message <3n_Tn.2420$Yo5.136@newsfe01.iad>...
> That policy will just lead to people routinely turning off "all 
> instances in file" of warnings without examination. The medicine will be 
> worse than the problem.

That, as you point out, would be bad programming practice too. I would discourage that as much as I would discourage having warnings left over.

> We turn off warnings only when we completely understand their causes and 
> know that the existing code is appropriate. Sometimes we don't 
> completely understand the code we have written or sometimes the warning 
> points out future work that should be done and turning off the warning 
> would hide that hint from us. As long as the warning is there it is 
> "nag-ware" prompting us to continue thinking about the issue.

See for an alternative (perhaps better) method for keeping track of hacks and todo items.

As I said in the beginning, this is my opinion on how to do things. There are infinitely many others, and the best one likely depends on the particulars of each situation. To each, his own.