From: Walter Roberson on
Yersinio Jimenez wrote:
> Dear Walter, thanks for your help.
>
> I think that this (mis) feature of MatLab is really really dissapointed.
> If you look around, many other programming languajes have backward
> compatibility, in example micro$oft with the dot net framework, for
> visual basic dot net and C sharp dot net programming languajes.
>
> With Matworks cant do the same thing with MCR??

MCR deals with internal unpublished interfaces, the choice of which may
be optimized for efficiency according to knowledge of the internals of
the library. .NET and C# and C deal with published interfaces -- C in
particular has a lot of inertia: it had some minor corrections 5 years
ago but major revisions only about once a decade.

If you look into the history of any particular Linux variant, if it has
lasted even half as long as MATLAB has, it has probably undergone
several upheavals in the binary interface, each one requiring recompilation.

And if you start working with free-source packages to any degree, one
thing you will find annoying is how often you have to update support
libraries -- having to update 50 of them representing hours of
compilation and a gigabyte of source, just to support a single bug fix
in the program you are interested in, is not at all uncommon.

Backwards compatibility is an exception rather than the rule.