[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empt
From: |
Nicholas Jankowski |
Subject: |
[Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b) |
Date: |
Mon, 14 Nov 2016 15:16:09 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 |
URL:
<http://savannah.gnu.org/bugs/?49601>
Summary: strmatch, incompatible result on 'empty' input, (and
still around in 2016b)
Project: GNU Octave
Submitted by: nrjank
Submitted on: Mon 14 Nov 2016 03:16:06 PM GMT
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name: Nicholas Jankowski
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.0.3
Operating System: Microsoft Windows
_______________________________________________________
Details:
This was just brought up over at stackoverflow:
http://stackoverflow.com/questions/40565761/octave-issue-runnig-matlab-file-at-if-x-0-strmatchxx
in Matlab 2016b:
strmatch(' ', ' ')
ans =
1
Octave 4.0.3:
>> strmatch(' ', ' ')
ans = [](0x1)
since the function is supposed to trim trailing whitespace, it appears Octave
deals with it as comparing empty inputs, producing empty outputs, while Matlab
does not.
Compatibility on handling empty inputs seems to have popped up a few places.
I realize this function has been on the 'will be deprecated list' for quite a
few years now, but it seems Matlab has been keeping it around so compatibility
fixes still make sense. especially if a fix isn't overly complicated
Are there any other similar functions we should check for similar behavior?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49601>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b),
Nicholas Jankowski <=
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Nicholas Jankowski, 2016/11/14
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Nicholas Jankowski, 2016/11/14
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Nicholas Jankowski, 2016/11/14
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Nicholas Jankowski, 2016/11/14
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Rik, 2016/11/14
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Rik, 2016/11/20
- [Octave-bug-tracker] [bug #49601] strmatch, incompatible result on 'empty' input, (and still around in 2016b), Guillaume, 2016/11/24