25 May
2007
25 May
'07
5:25 a.m.
But I really like the look of the following code:
bm_type::map_by<name>::const_iterator_range r = bm.equal_range(...);
bm_type::map_by<name>::iterator_range r = bm.range(...,...);
Are you against provide these typedefs?
not at all.
Ok, I will add them.
(maybe with another name: sub_range, range, range_type)
simply "range" and "cont_range" is more concise IMO. The relation to iterators is immplied.
Boost.MultiIndex and Boost.Bimap defines a function "range(... , ...)". We can not use the name range for the typedef... :( I vote for range_type and const_range_type ( Note that we can not change the range function signature because MultiIndex has use it for years ) Best regards Matias