Jody Hagins wrote:
I see that the implementation of type_id is chock full of special code. There appears to be so much difference between how compilers handle stuff (the shared lib problem documented in the header is especially disturbing).
However, this does not seem to be isolated just to using Boost.Python, so is it possible to have it moved somewhere else more common, like boost/type_id.hpp or something similar which makes it more widely available?
The way these things are handled is as follows: if another Boost library wants to use facilities that are an implementation detail of an existing Boost library, they are moved into boost/detail by the author of the former library. If someone wants to make the functionality available to users, that person moves it into namespace boost, documents it, and writes tests. Then the library goes through a fast-track review process. I'm happy to have either of those things happen to that code, but I'm not volunteering to do any of the work ;-) -- Dave Abrahams Boost Consulting http://www.boost-consulting.com