The spate of questions regarding BOOST_FOREACH
prompts me to ask users of the Boost library what (if anything) they are doing to prepare their code for portability
The simple answer is "do nothing". Boost is not going to remove the libraries that got adopted into 0x. So boost::shared_ptr will still exist. So you don't need to do anything to maintain portability.
Of course, once 0x is here, a lot of code can be simplified, cleaned up and optimized, but since it's not yet here, that work can't really begin. All you can do is make sure your code will still compile when 0x hits... and it should, just like that. Boost isn't going to delete half their libraries. (I'm not guessing. They've stated this on their mailing list before)
(and if you want to switch to the standard shared_ptr, I'd say it's probably easier to just do a simple search/replace when the time comes. Replace #include
with #include
, and boost::shared_ptr
with std::shared_ptr
)
Or of course, you can just decide on the project that you're going to keep using Boost's shared_ptr
. Just because it's been added to the standard library doesn't mean you have to use it, after all.