|
From: | John W. Eaton |
Subject: | Re: Rethinking octave_idx_type |
Date: | Fri, 25 Nov 2016 12:38:14 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 |
On 11/25/2016 12:33 PM, Mike Miller wrote:
Do you have a reason to prefer a signed type rather than an unsigned size_t? Using a size_t would make Array<T> more compatible with STL container definitions.
We have a number of places where we use -1 to indicate "not defined". So as a first pass, using a signed type will be easier. Once that works we could consider just using size_t and fixing the places where negative values are used or possible.
jwe
[Prev in Thread] | Current Thread | [Next in Thread] |