[Octave-bug-tracker] [bug #61750] ismember does not report all matches

[Nicholas Jankowski]

Follow-up Comment #8, bug #61750 (project octave):

ok, had to dig a little to find a description of what 'legacy' changed. turns
out it seems it only has to do with ordering of the second argument and
handling of some specialized matlab classes. 

The old inline help for ismember before the change stated:

"In a future release, the behavior of ismember will change including:
  - occurrence of indices in LOCB will switch from highest to lowest
  - tighter restrictions on combinations of classes"

as per: https://stackoverflow.com/a/20497078/4598449

from the current help:

The 'legacy' option does not support categorical arrays, datetime arrays,
duration arrays, tables, or timetables.


it seems the impact is only on classes octave doesn't yet support anyway. 

So, if my reading of the code and comment #6 is correct, the bug could be
fixed and compatibility enhanced just by making a 'legacy' flag whose only
function  is to flip the call to unique from 'last' to 'first'. 

would want a set of compatibility-validated BISTs though to make sure it's not
more than that.

    _______________________________________________________

Reply to this item at:

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

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