Hello, That is great news, one of the most missing features. Several questions: a) Does it rename macros as well? I mean if I have a library with defined BOOST_ASIO_ENABLE_FOO_BAR would it be renamed to NEWNAME_ASIO_ENABLE_FOO_BAR ? b) Doest it updates BJam files as well. c) How do you deal with various test files? d) Have you tryed to run some regrssion tests? I had written once such tool on my own, see http://lists.boost.org/boost-build/2009/05/21911.php http://cppcms.svn.sourceforge.net/viewvc/cppcms/framework/branches/refactoring/tools/rename.py?revision=935&view=markup However I hadn't updated the BJam files. I still managed to build most of parts of boost and run some regession test. I would defenatly test it ASAP. Artyom
Also changes library names to start with the prefix "newname" or "libnewname" rather than "boost" or "libboost".
Does it changes include paths as well? So I can include <newname/shared_ptr.hpp>
What you can not do at present, is #include two different boost versions in the same translation unit.
When you use alias or in any case? Actually my tool had allowed this. Why you can't do this? Artyom. P.S.: This is very important step!