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

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

[Octave-bug-tracker] [bug #36555] strfind() should work with numeric arr


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #36555] strfind() should work with numeric arrays
Date: Tue, 16 Nov 2021 19:43:12 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36

Follow-up Comment #7, bug #36555 (project octave):

just noting this is still present in Octave 6.4.0., suggesting it be closed as
a 'won't fix' until someone really wants to make it happen. it lives in c++
space vs m-space, so that limits number of people who might mess with it to
people with generally more important things to work on.

Also, this is clearly undocumented behavior. Matlab docs are usually fairly
clear with accepted input types. for strfind it states:


str — Input text
string array | character vector | cell array of character vectors

https://www.mathworks.com/help/matlab/ref/strfind.html

As Rik said the simple input validation hack wasn't enough to make this work.
Now, if the quick fix works for all but floats/complex, maybe an input_check
could be added to the hack to throw an error specifically for those while
allowing integer inputs to pass and therefore provide partial undocumented
compatibility. Maybe a 'partial undocumented compatibility' note could be
added to the docstring.

But simply closing as a won't fix seems quite appropriate as well. 

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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