[Octave-bug-tracker] [bug #36743] Octave:matlab-incompatible warning warns about Octave's own files

[Carnë Draug]

Follow-up Comment #5, bug #36743 (project octave):

Maybe this warning ID ought to just be removed completely.

Here's my argument. This warning ID is only useful to write Matlab code. For
that purpose, it needs to identify Octave only syntax (auto-increment,
double-quotes, endifs, etc) and use of functions with options not present in
Matlab.

We are only covering the first case which is very very easy for the user to
identify visually, and an even easier job for any text editor (exception for
automatic broadcasting).

The second case is much more difficult for the user and therefore the most
useful. This would require us to go through all the octave code, and throw
warnings when a specific codepath is followed (for example, calling linspace()
with a vector instead of scalar). For it to work properly, according to this
bug report, it would also require that a function knows if it's being called
by a "user" or a "core/library" function. We shouldn't be polluting all the
octave and packages code with such warnings, that would be a lot of work to
start, and a lot of maintenance.

If we are not going to cover the second case, this warning is pretty much
useless and will only provide a false sense of security to the user.  We might
as well remove and be done with this.

Also, I wonder how much of a performance issue is to check at every endif,
endfunction, autoincrement, automatic broadcasting, etc, the warning status of
the id.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36743>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/