Re: [boost] [Range] Confusing result of iterator_range::size()

Subject: Re: [boost] [Range] Confusing result of iterator_range::size()
From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2011-11-03 08:06:47

Den 03-11-2011 10:35, Sergey Voropaev skrev:
> Thorsten Ottosen<thorsten.ottosen<at>  dezide.com>  writes:
>
>>
>> The min() example that fails to compile is tricky...
> This example is derived from real valid code.
>> Even if we make it
>> unsigned, size_types may differ (e.g. a 32 bit unsigned int and a 64 bit
>> size_t).
> 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.

-Thorsten