[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47036] regressions in core m-files due to ism
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes |
Date: |
Tue, 02 Feb 2016 18:55:45 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #8, bug #47036 (project octave):
Actually, the most common reason to use isnumeric is to keep out cell arrays.
People often view arrays or cells as just data containers and think they
should be able to use one in place of the other. And as you say, it leads to
cryptic error messages.
tetramesh (C, X)
error: cell type invalid as index value
error: called from
tetramesh at line 101 column 15
error: evaluating argument list element number 4
error: called from
tetramesh at line 101 column 15
I don't think we need to be utterly rigorous, since there is a small
performance hit to always checking the inputs. If the chances are low that
anyone will think to call the function with a cell array then we can skip
using isnumeric in that case. I will say that the plot routines are not
terrifically time sensitive so they could have the extra checking and it would
be fine, but you don't need to do it if you don't feel like it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47036>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/01
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/01
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/01
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Rik, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Rik, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes,
Rik <=
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Lachlan Andrew, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Michael Godfrey, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Rik, 2016/02/02
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/03
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/03
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Colin Macdonald, 2016/02/03
- [Octave-bug-tracker] [bug #47036] regressions in core m-files due to ismatrix changes, Rik, 2016/02/08