octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #50776] Octave inconsistent with Matlab for co


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #50776] Octave inconsistent with Matlab for corner indexing case
Date: Wed, 12 Apr 2017 09:03:07 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0

Follow-up Comment #6, bug #50776 (project octave):

Thanks for the pointer to the blog post.  It doesn't seem to mention anything
about N-d "vectors".

And yes, this may be inconsistent with the isvector function, but I still
think we should probably be consistent with Matlab here.

"This is really a consequence of the fact that any logical array index is
first converted to a column vector. And then the general rule is that for
vector/vector operations it is the indexed object whose size is retained. "

Shouldn't that be "converted to a column vector if it is not already a
vector"?  Otherwise, wouldn't the result of array(logical_row) be a column
vector?  I think it ends up being a row.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]