Also noting that all this apparently has been triggered by a user that wants
to run Matlab code that has gone unchanged for ~13 years. No opinion on
that [*], but rather at consequences for our priorities.
Matlab compatibility is one of the biggest foundations of Octave's success
but I sometimes wonder how far the octave project should go in exactly
mimicking Matlab behavior, in this case informing about obsoleteness.
What is the compatibility target anyway: the very newest Matlab release, or
do we lag behind a few releases? (we already do w.r.t. several things: v7.3
mat files & classdef, new string class, table class, object-based graphics.)