I've started working through bimap in preparation for a review, but I'm having a few problems with the source: Gcc on linux, passes all the tests (tried AMD64 and IA64), good :-) Intel 9.1 on Linux, and HP aCC on HP-UX fails to build quite a few tests. These compilers are both based on a recent release of the highly regarded EDG front-end, and may indicate issues with the source. The HP aCC test run produced a 17Mb log file of errors and warnings (!) which is um, rather alarming so I'll contact Matias by private email with the logs. On Win32, everything builds with msvc, but I'm seeing access violations in: test_bimap_assign test_bimap_property_map with all of VC7.1, VC8, Intel 8.1 and 9.1. There are a few warnings as well that look suspicious to me: c:\data\boost\develop\boost\boost\multi_index\detail\ord_index_node.hpp(127) : warning C4312: 'type cast' : conversion from 'boost::multi_index::detail::uintptr_type' to 'void *' of greater size c:\data\boost\develop\boost\boost\multi_index\detail\ord_index_node.hpp(132) : warning C4311: 'type cast' : pointer truncation from 'void *' to 'boost::multi_index::detail::uintptr_type' c:\data\boost\develop\boost\boost\multi_index\detail\ord_index_node.hpp(159) : warning C4312: 'type cast' : conversion from 'const boost::multi_index::detail::uintptr_type' to 'void *' of greater size And finally, the serialization test fails to build with VC8 with: c:\data\boost\bimap\libs\bimap\test\test_bimap_serialization.cpp(53) : error C2872: 'bimap' : ambiguous symbol could be 'c:\data\boost\bimap\boost\bimap\bimap.hpp(149) : boost::bimap::bimap' or 'boost::bimap' c:\data\boost\bimap\libs\bimap\test\test_bimap_serialization.cpp(53) : error C2872: 'bimap' : ambiguous symbol could be 'c:\data\boost\bimap\boost\bimap\bimap.hpp(149) : boost::bimap::bimap' or 'boost::bimap' I note from the docs that these compilers are all listed as supported, so I'm guessing that either recent changes to Bimap, or to Boost cvs have broken something. Anyway I thought I'd bring these up in the hopes that there are some easy fixes, before other reviewers hit the same issues. I'll get back to reading the docs now :-) Regards, John.