[Octave-bug-tracker] [bug #51187] ISMEMBER fails if the string ends in a space:

[Philip Nienhuis]

Follow-up Comment #9, bug #51187 (project octave):

OK I checked and it turns out that Matlab r2012a and r2016b behave differently
as regards char arrays. For simple character strings (1D vectors) the behavior
is as I wrote in comment #8:

R2016b
======

>> format compact
>> ismember ('b ', {'a ', 'b '})
ans =
  logical
   1
>> abc = ['a '; 'b '; 'c ']
abc =
a 
b 
c 
>> ismember (abc, {abc})
ans =
  3×1 logical array
   0
   0
   0
>>


However with r2016b:

>> abc = ['a '; 'b '; 'c ']
abc =
a 
b 
c 
>> ismember (abc, {abc}, 'legacy')
ans =
  3×1 logical array
   1
   1
   1
>>


R2012a
======

>> format compact
>> ismember ('b ', {'a ', 'b '})
ans =
     1
>> 
>> abc = ['a '; 'b '; 'c ']
abc =
a 
b 
c 
>> ismember (abc, {abc})
ans =
     1
     1
     1
>> ismember (abc, {'a '})
ans =
     1
     0
     0
>> ismember (abc, {'a ', 'b '})
ans =
     1
     1
     0
>> ismember (abc, {'a '; 'b '})
ans =
     1
     1
     0
>> ismember (abc, {['a '; 'b '; 'c ']})
ans =
     1
     1
     1
>> 


The 'legacy' option seems to have been made especially for Tables and other
new stuff like datetime arrays, duration arrays and timetables; although it
existed already in r2012a where it apparently was meant to relax stricter
rules regarding input types.
I wonder if treatment of 2D char arrays in recent matlab releases might have
been an unintended "regression".
I didn't find info in Matlab's release notes, so I might enter a bug report
for it in the Mathworks site.


    _______________________________________________________

Reply to this item at:

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

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