Jason Winnebeck wrote:
But this leads to another question: If I compile my library with Boost x but the user has Boost y installed when he links with my library (I DO pass shared_ptr back and forth between user code, so it's not just used internally), what will happen? The shared_ptr interface seems to be oft changing, and so right now my code would only compile for Boost 1.30 (or later?
shared_ptr has recently been accepted into the Library Technical Report: http://std.dkuug.dk/jtc1/sc22/wg21/docs/library_technical_report.html http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1450.html Since modifications to the TR draft require a full committee vote, shared_ptr's interface will be much more stable now. Binary compatibility is another story. 1.30.x, 1.31.x and 1.32.x will likely be incompatible. But this is only an issue if you're shipping prebuilt binaries, not source.