Path: news.mathworks.com!newsfeed-00.mathworks.com!news.tele.dk!feed118.news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!t-online.de!newsfeed.t-com.hr!news3.t-com.hr!not-for-mail
From: Roni Miholovic <rmiholovic@invalid.com>
Newsgroups: comp.soft-sys.matlab
Subject: matlab backward compatibility options
Date: Wed, 23 Sep 2009 15:14:26 +0200
Organization: T-Com
Lines: 16
Message-ID: <qc7kb55dcr79ugopnv3nmmnfhkcva1r6vt@4ax.com>
NNTP-Posting-Host: 93-136-6-249.adsl.net.t-com.hr
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: ss408.t-com.hr 1253711666 22085 93.136.6.249 (23 Sep 2009 13:14:26 GMT)
X-Complaints-To: abuse@t-com.hr
NNTP-Posting-Date: Wed, 23 Sep 2009 13:14:26 +0000 (UTC)
X-Newsreader: Forte Agent 5.00/32.1171
Xref: news.mathworks.com comp.soft-sys.matlab:572320

I've searched but couldn't find anything on the subject. The other
day, there were some talks at my company about acquiring a few matlab
licences for projects on a long term basis (we have some fortran code
from the sixties still in active use). 

And one of the subjects that came up was whether matlab has some
official policy regarding backward compatibility - I, for once,
haven't been able to find it.

Does anyone know what is mathworks's stand on this, and how does
matlab rank practically when it comes to backwards compatibility ? For
example, on the current version, what is the oldest active code which
will still run without any modifications ?

with regards,
Miho