[Octave-bug-tracker] [bug #50583] Empty arguments to some simple functions give inconsistent results to Matlab

[Rik]

Update of bug #50583 (project octave):

                Category:                    None => Octave Function        
                Severity:              3 - Normal => 2 - Minor              

    _______________________________________________________

Follow-up Comment #1:

This is a philosophical difference.  Octave has generally preferred to raise
an error early to alert the programmer that something is wrong.  The
alternative, which Matlab often does, is to keep computing but use the value
NaN.  The NaN value cascades through calculations so at the end of a long
script the programmer may find that the value is NaN, but have no idea which
step in the process created the problem.  I wouldn't change Octave's behavior
in this case, rather I would make sure that mode and cov also issue errors. 
But we'll see if other core programmers have an opinion.

    _______________________________________________________

Reply to this item at:

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

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