Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Matlab bugs
Date: Tue, 2 Sep 2008 19:35:04 +0000 (UTC)
Organization: UMN
Lines: 20
Message-ID: <g9k4h7$957$1@fred.mathworks.com>
Reply-To: <HIDDEN>
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 1220384104 9383 172.30.248.37 (2 Sep 2008 19:35:04 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Tue, 2 Sep 2008 19:35:04 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 870237
Xref: news.mathworks.com comp.soft-sys.matlab:488308



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.