Path: news.mathworks.com!not-for-mail
From: "Rodney Thomson" <readmore@iheartmatlab.blogspot.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Matlab bugs
Date: Wed, 3 Sep 2008 01:24:02 +0000 (UTC)
Organization: The MathWorks, Inc.
Lines: 39
Message-ID: <g9kovi$rgr$1@fred.mathworks.com>
References: <g9k4h7$957$1@fred.mathworks.com>
Reply-To: "Rodney Thomson" <readmore@iheartmatlab.blogspot.com>
NNTP-Posting-Host: webapp-02-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1220405042 28187 172.30.248.37 (3 Sep 2008 01:24:02 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Wed, 3 Sep 2008 01:24:02 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 1430350
Xref: news.mathworks.com comp.soft-sys.matlab:488341



"Jeremy Smith" <smit1729@umn.NOSPAM.edu> wrote in message
<g9k4h7$957$1@fred.mathworks.com>...
> One of my coworkers recently found a problem/bug in the
> datenum function of Matlab 7.0.  It was adjusting for
> daylight savings time so we were left with some of our data
> being shifted by an hour.  This was fixed in later versions
> of Matlab however nothing about daylight savings time was
> mentioned in the documentation or revisions list of Matlab.
> 
> Where does a researcher have to go to find information about
> changes that significantly impact code execution?  How is
> anyone suppose to check all of their old code to make sure
> it works with newer versions of Matlab?
> 
> We need a tool which can check an m-file and give a nicely
> formatted report on what changes have been made to all its
> functions between two versions of Matlab.  This includes
> argument syntax, default settings, phasing out functions,
> and speed.  The researchers I work with are very close to
> getting everyone on the same version of Matlab and declaring
> an indefinite embargo on updating Matlab.  We already work
> with a researcher who has done this.

Updating a revision of MATLAB, GCC, Visual Studio, Perl,
Ruby, etc etc etc always comes at the risk of changing
behavior. You should never assume consistent behaviour,
particularly across major revision changes.

Before upgrading, check the release notes of all newer
releases (ie 2008 is here -
http://www.mathworks.com/access/helpdesk/help/base/relnotes/)

Rod

--
http://iheartmatlab.blogspot.com