9 Dec
2005
9 Dec
'05
11:11 p.m.
Thorsten Ottosen wrote:
I think this might be a bug in the compiler.
I thought it was intentional. See:
void test() { std::string str;
// hey, const sub_range. const boost::sub_rangestd::string rng1(str);
// whether or not to allow...? boost::sub_rangestd::string rng2 = rng1; }
I don't know the answer for sure.
Can you assing a const vector<T> to a mutable vector<T>?
Hmm, yes. (though I think it is not the property of range.) I believed it was your intention, because a trivial assignment fails like Victor's example under VC++7.1. I must change the recognition of sub_range. Regards, MB http://p-stade.sourceforge.net/