------- Comment #20 from pcarlini at suse dot de  2006-04-20 11:56 -------
Everything considered, I don't think there is something to fix here, either in
the compiler (and all the other compilers I tried bahaves the same of current
g++ on Comment #18, irrespective of the position of the overloaded operator, of
course) or in the library: agreed, std::fill_n could be made more robust
restricting the second template argument, but this is really matter for C++0x.
Otherwise, the problem would immediately go away if vector<>::iterator were a
plain pointer, but that is not an option for our implementation.

Agreed?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26974

Reply via email to