Bjørn Roald wrote:
If a bcp based solution becomes useful, I think it should be considered to be included in the tool in the boost distribution.
Sounds interesting enough to be worth adding: regex based search and replace of namespaces should be easy enough?
As the figure illustrate, bcp is a one way tool when you change the namespace. I feel strongly that the tool shall be used as a build step rather than keeping the modified code under local source control. The better way is to do modifications, patches, testing and contributions for boost as other boost users. Then use bcp as a build-time tool.
To reduce overhead introduced by this build-time, I added an option to my bcp version which in case the target file exist only will overwrite if file content changes. This reduces build time dramatically for changes after initial build.
Also a good idea, as long as it's an option: sometimes you want to overwrite the existing file :-) John.