|
| From: | Carlo de Falco |
| Subject: | [Octave-bug-tracker] [bug #48439] validateattributes throws errors without IDs |
| Date: | Tue, 12 Jul 2016 07:19:19 +0000 (UTC) |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:47.0) Gecko/20100101 Firefox/47.0 |
Follow-up Comment #3, bug #48439 (project octave):
The new attachment file #37820 produces a list of all
error ids produced by validateattributes in Matlab when
the input argument does not satisfy a given condition,
the results are the following:
>> va_ids
MATLAB:expected2D
MATLAB:expected3D
MATLAB:expectedColumn
MATLAB:expectedRow
MATLAB:expectedScalar
MATLAB:expectedVector
MATLAB:incorrectSize
MATLAB:incorrectNumel
MATLAB:incorrectNumcols
MATLAB:incorrectNumrows
MATLAB:incorrectNumdims
MATLAB:expectedSquare
MATLAB:expectedDiag
MATLAB:expectedNonsparse
MATLAB:notGreater
MATLAB:notGreaterEqual
MATLAB:notLess
MATLAB:notLessEqual
MATLAB:expectedBinary
MATLAB:expectedEven
MATLAB:expectedOdd
MATLAB:expectedInteger
MATLAB:expectedReal
MATLAB:expectedFinite
MATLAB:UndefinedFunction
MATLAB:expectedNonnegative
MATLAB:expectedNonZero
MATLAB:expectedPositive
MATLAB:expectedDecreasing
MATLAB:expectedIncreasing
MATLAB:expectedNondecreasing
MATLAB:expectedNonincreasing
when the input argument does not match the expected type
the ID is always 'MATLAB:invalidType'
would it be OK to introduce all the same error IDS mapping
the names to Octave style as
MATLAB:expectedXxxx -> Octave:expected-xxxx
MATLAB:invalidType -> Octave:invalid-type
?
Should we also keep the generic error ID
"Octave:invalid-input-arg"
?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48439>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |