如何处理一些使用频繁的库的逐步重构？(How to handle step-by-step refactory of some heavily used libraries?)

 我有几个针对多个平台的库，其中一些是实时/不具备STL支持的实时库，更不用说tr1或C ++ 11了。 这意味着一切都使用库自己的字符串/数组/列表/ younameit类。 现在这些平台已经被抛弃，转而支持'纯'C ++ 11和STL（我非常高兴：我做的最新的lib是第一个带有新标准的开发时间，开发时间缩短了很多，而代码质量上升）。 
 
 现在我希望新项目不依赖于自定义字符串/数组/ ...类，我打算一步一步地重构：每当我需要一些类时，创建一个副本（不是完整的）重复;仍然有点痛，但有另一种选择吗？）而是使用STL。 在一开始，这可能意味着整个类树可能需要立即更改。 同时原始代码应该在接下来的4年左右继续工作。 
 
 实际上我现在面临的主要问题是：我在哪里放这些新课程？ 例如 
 
A\A.h depends on B\B.h and string.h
 
 应该成为 
 
a new A.h depending on a new B.h and <string>
 
 我是否新建了NewA课并加入了Ah？ 或者在新的命名空间中创建一个A类并将其存储在A\newA.h ？ 或者我创建一个全新的子目录结构，如new\A\Ah和new\B\bh ？ 
 
 我知道已经有几个类似的问题，有很好的答案，但我想要一些更实用的建议，而不是“阅读有效使用遗留代码”。 虽然这是理智的答案，但我对你在类似情况下的实际行动更感兴趣？ 
 
 编辑一些说明： 
 
 
 
 大多数当前应用程序也将被移植到及时使用STL，因为它们都将在新平台上运行（仍然对RTX或InTime有疑问，但其中之一）。 
 
 
 我确实使用了VCS，git，而且几乎所有重要的东西都被单元测试所覆盖。 否则这将是疯狂的。 
 
 
 没有真正的团队，而且我自己（不幸的是，当涉及到这样的事情时，我无法将我的同事视为团队成员，虽然我的年龄几乎是我的两倍，他的编程水平不到我的一半，而且我是甚至不熟练。 
 

I have a couple of libraries that were targetting multiple platforms, of which some realtime ones that did/do not have decent STL support, let alone tr1 or C++11. This means everything uses the library's own string/array/list/younameit classes. Now these platforms are getting abandoned in favour of 'pure' C++11 and STL (which I am very very glad for: the latest lib I did is the first one with the new standard and development time has shortened a lot, while code quality went up).
 
Now I want new projects to not depend on the custom string/array/... classes, and I'm planning to go for a step-by-step refactory: whenever I need some class, create a duplicate (well not a complete duplicate; still that hurts, but is there another option?) that uses STL instead. In the beginning that might mean a whole tree of classes might need changing at once. At the same time the original code should keep working for the next 4 years or so.
 
Practically the main question I'm facing now is: where do I put these new classes? For example
 
A\A.h depends on B\B.h and string.h
 
should become 
 
a new A.h depending on a new B.h and <string>
 
Do I make a new class NewA and put in in A.h? Or make a class A in a new namespace and store it in A\newA.h? Or do I make a whole new subdirectory structure like new\A\A.h and new\B\b.h?
 
I know there are already a couple of similar questions, with great answers, but I'd like some more practical advice, not "read Working Effectively with Legacy Code". Though that is, with reason, a good answer, I'm more interested in what you practically did in a similar situation? 
 
edit some clarification:
 
 
 
The majority of the current applications will also be ported to use STL in time as they will all run on the new platform (still in doubt about RTX or InTime, but one of those).
 
 
I do use a VCS, git, and pretty much everything that matters is covered by unit tests. Else this would be madness.
 
 
There's no real team and I'm on my own (unfortunately I cannot count my collegue as a team member when it comes to things like this, though being almost twice my age his programming level is less then half of mine, and I'm not even that skilled. 
 

原文：https://stackoverflow.com/questions/7244471