Subject: Re: [boost] [Range] Confusing result of iterator_range::size()
From: Sergey Voropaev (serge-voropaev_at_[hidden])
Date: 2011-11-03 08:18:07
Thorsten Ottosen <thorsten.ottosen <at> dezide.com> writes:
> Den 03-11-2011 10:35, Sergey Voropaev skrev:
> > Thorsten Ottosen<thorsten.ottosen<at> dezide.com> writes:
> > Yes, but mostly all well-known containers use size_t as size_type.(I can
> > imagine
> > container with 64 bit unsigned size in 32 bit programm, but it is not common
> > case). But using 32 bit int for size in programm will be error of programmer
> > but not error of container design. Container with signed int as size_type is
> > very unusual container.
> Why? Its not uncommon to use 32 bits for storing size/capacity in vector
> like containers, even for 64 bit development.
Sorry, but I do not say it. I say its common to use size_t for storing
size/capacity. And its non common to use signed. It is very confusing for me as
user of your library.
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk