[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47416] call of overloaded 'octave_value(Array
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #47416] call of overloaded 'octave_value(Array<int>&)' is ambiguous |
|
Date: |
Sun, 03 Apr 2016 19:27:45 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #12, bug #47416 (project octave):
I think sized int types are always better, and are more consistent with the
way integers are used throughout Octave already.
If more constructors are added, what type of octave_value should the following
produce?
Array<int32_t> x (dim_vector (1, 1));
x(0) = 42;
octave_value ov (x);
Right now, it matches the Array<octave_idx_type> and converts into an
octave_matrix (a double-valued array).
I'm in favor of sized int types, but I think adding more constructors may end
up adding confusion or breakage.
Users should use int32NDArray if that's what they meant to return.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47416>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/