How do you say, the following things are some of my recent thinking.
Re-use is a big category, whether it is the multiplexing of the code or the multiplexing of the module. For multiplexing, there are two features -
Unity
public.
These two features are particularly obvious on STL (code multiplexing) and COM (module multiplexing). For example, the coupling between the containers and its elements, this is known about the TRATS Pattern implementation of Iterator, which has been well explained; another, for generic algorithms The coupling between them follows the standard of the iterator, and does not care about the container, the specific implementation of the element. In COM, they follow more standards, such as unified calling methods, common IunkNown base classes, and more.
There is no need for me, multiplexing makes software development simpler, more efficient - there is a great convenience.
Some of them are not multiplexed, such as Qin Shihuang's unified text and scale.嬴 嬴 This buddy is definitely not for multiplexing, but the effect is the same - brought great convenience.
