18 May
2010
18 May
'10
1:40 p.m.
The assumption that a library client can, or should be able to, use whatever Boost build they happen to have lying about with their code while using a third party library built with another version of Boost is the problem.
This is exactly what today's build/autoconfiguration schemes will do in most cases. If the library client is configured to depend on libfoo (compiled against a boost other than the system boost) and boost, autoconfiguration will normally cause symbols from both the system boost and libfoo's boost to collide in the resulting code. As boost is by design likely to create ABI incompatible symbols with different versions, a robust, user-controllable name mangling facility would be useful. Best regards, Isidor