I prefer size_t.
On 22 November 2012 12:53, Johan Hake <[email protected]> wrote: > I have no objection to "size_t". As Garth says, it would also make sense > to use uintp, which is the NumPy equivalent, but then we should consider > using float_ or float64 instead of double, which is unintuitive. > > Johan > > On 11/22/2012 12:00 PM, Anders Logg wrote: > > On Thu, Nov 22, 2012 at 10:41:10AM +0000, Garth N. Wells wrote: > >> On Thu, Nov 22, 2012 at 10:22 AM, Anders Logg <[email protected]> wrote: > >>> Why is the type called 'sizet' and not 'size_t' in the Python > >>> interface for templated MeshFunctions? > >>> > >> > >> The appropriate name was raised as a question when the changes were > >> made. It could be sizet, size_t, uintp (numpy type), uint, etc. > > > > I prefer size_t over sizet since it matches the C++ interface and does > > not introduce yet another type. > > > > -- > > Anders > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~dolfin > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~dolfin > > More help : https://help.launchpad.net/ListHelp > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~dolfin > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dolfin > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : [email protected] Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
