What version of MATLAB do you code against

Inspired by: http://www.mathworks.com/matlabcentral/answers/16427-difference-between-matlab-6-1r12-1-and-matlab-7-13r2011a

I was curious about what version of MATLAB people code against (i.e., ensure there program works). For a few years I was trying to ensure backwards compatibility with MATLAB 6 (something or other), but once the new OOP system was introduced, I gave that up. Now I assume that my users are running at least the version I am running and hope that the new versions do not introduce any bugs that break what I am doing.

Answer 1

[Aurelien Queffurust]

I ensure my codes work from R2007b to the current release. R2007b is just because some end-users are still working under Windows 2000 which is the latest MATLAB release supported for this OS.

[Daniel Shub]

I like that. Maybe I will start thinking about what OS's I want my code to run on and code for the latest version supported for that OS. It is much easier to ask someone to update MATLAB, much harder to ask them to change OS.

Answer 2

[Jan]

I test my codes under 6.5, 7.0, 2008b, 2009a and 2011b.

I've added some version depending patchs for the older versions, e.g. BSXFUN, TYPECAST, ANCESTOR, COMMANDWINDOW, SAVEPATH, ... I'm running 6.5 in a virtual XP box, such that the updates of the OS do not matter very much.

Versions before 6.5 have too many limitations: No dynamic fieldnames, no consistent short-curcuiting, inconsistencies in the Mex-API (mxCreateDoubleScalar - mxCreateScalarDouble, LOGICAL arrays have been DOUBLE arrays with an extra flag, etc).

The C-Compilers are a problem also: The builtin LCC version was outdated even in 6.5, therefore I'm using a downloaded version. It works for 2009a also, but the mexopts.bat file needs some smart modifications. BCC5.5 and OpenWatcom1.8 are more powerful than LCC, but they are not compatible to 2009a and I did not find out how to deliver the runtime libs of OWC. Finally I'm running a bunch of MSVC compiler versions...

Answer 3

[Image Analyst]

I always upgrade to the current version within a couple of weeks after it was released. I compile most of my apps for my users so they're always on what I have after I compile and deploy a new version. A few of my users use the full MATLAB and I ask them to upgrade as soon as they can. It's just much easier this way, rather than having to test my code on multiple prior releases.

Answer 4

[James Tursa]

32-bit Windows XP R2006b - R2011b (R2012a once I get it installed). Since all of my submissions are mex routines, I run against lcc and MSVC compilers to try and detect version specific oddities/errors with regards to the API. I have to rely on other users for 64-bit debugging help, but that may change in the near future as I may be moving to a Windows 7 machine. I think one of these days I will need to publish a "mex programming guide" to consolidate all of the tips etc that I have learned over the years.