C.122: Use abstract classes as interfaces when complete separation of interface and implementation is needed
C.122:需要完全隔离接口和实现时使用抽象类作为接口
Reason(原因)
Such as on an ABI (link) boundary.
类似ABI边界的做法。
ABI：https://baike.baidu.com/item/ABI/10912305
Example(示例)
<code>structDevice{
virtual~Device()=default;
virtualvoidwrite(span<constchar>outbuf)=0;
virtualvoidread(span<char>inbuf)=0;
};
classD1:publicDevice{
//...data...
voidwrite(span<constchar>outbuf)override;
voidread(span<char>inbuf)override;
};
classD2:publicDevice{
//...differentdata...
voidwrite(span<constchar>outbuf)override;
voidread(span<char>inbuf)override;
};/<char>/<constchar>/<char>/<constchar>/<char>/<constchar>/<code>A user can now use D1s and D2s interchangeably through the interface provided by Device. Furthermore, we can update D1 and D2 in ways that are not binary compatible with older versions as long as all access goes through Device.
用户可以通过Device提供的接口自由地使用D1或D2的对象。除此之外，只要是通过Device访问，我们甚至可以将D1和D2更新为与旧版本不兼容的二进制形式。
Enforcement(实施建议)
???
原文链接
https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#c122-use-abstract-classes-as-interfaces-when-complete-separation-of-interface-and-implementation-is-needed
觉得本文有帮助？请分享给更多人。
更多精彩文章请关注微信公众号【面向对象思考】！
面向对象开发，面向对象思考！
閱讀更多 面向對象思考 的文章
