[Octave-bug-tracker] [bug #61295] cross() dimensions inconsistent with Matlab when using mismatched input vector dimensions

[Rik]

Follow-up Comment #3, bug #61295 (group octave):

My vote would be for solution #2: Matlab-compatible row vector output.  I
would certainly put a note in the NEWS file for 10.1.

When it comes to something like matrix-by-vector multiplication, the
orientation is quite important.  But, when it comes to vector-by-vector
operations it is important to distinguish whether the vector is really a just
a 1-D list data structure.  I think many programmers, in these cases, just
lose track of whether it is a row or column vector because it isn't very
important.  In the case of cross() with two vectors, I think it is enough for
Octave to recognize that they are vectors and hence it's not terribly
important whether they came is as row or column vectors.  And with that view,
we might as well adopt whatever output convention Matlab has since the choice
is arbitrary.



    _______________________________________________________

Reply to this item at:

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

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