Edward Diener-3 wrote
If anyone changes anything in a library which breaks anything else it is that person's responsibility to fix things. This is true whether it is MPL or anything else.
Agreed. The problem is that people who just need a small fix sometimes fail to appreciate the subtle repercussions of that that fix. They go ahead and do it and then figure they're done - sometimes without even running the whole test suite. I don't have an alternative idea. One thing that might be useful would be to set an explicit policy like "MPL is only guaranteed to works with: MSVC 8.0 and above GCC ?? and above etc. I wouldn't suggest anyone go in an start ripping out support for all the old stuff. But if someone is in there in the course of fixing something else, it would be fine - especially since it can't be tested anymore anyway. -- View this message in context: http://boost.2283326.n4.nabble.com/mpl-multiset-tp4672187p4672394.html Sent from the Boost - Dev mailing list archive at Nabble.com.