[Octave-bug-tracker] [bug #65544] cross.m: vector dimension should produce error, can produce erroneous result

[Nicholas Jankowski]

Follow-up Comment #2, bug #65544 (group octave):

minor update pushed to
https://hg.savannah.gnu.org/hgweb/octave/rev/2aea823a9973
(just noticed bug number typo in commit msg)

changed back the vector mismatch check as i misinterpreted what would sneak
through the original check, and the performance is slightly better with the
previous version.  Also adjusted the dim 3 element check so it would hit the
same error message whether x or y was sized. 

comment on bug #65527 indicated the input validation changes perhaps should go
on default. In this case, the original cases were either inconsistently
triggering lowel level errors with less meaningful messages or were silently
producing incorrect results. As such I felt stable was appropriate.  If this
should be moved to default instead i can back it out and move it.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65544>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/