A one-to-one relationship was established between proxy and invoker objects, with the explicit interface being the common association.
代理和调用程序对象之间建立了一对一的关系，而显式接口则充当了常用的关联方式。
A partial "service Generator" was written that generated skeleton code for proxy, invoker, and service classes from an explicit interface.
“服务生成器”的功能是根据显式接口为代理、调用程序和服务类生成框架代码，它已经被部分编写出来。
If a service supporting the required explicit interface was found in the local repository, a direct reference to the service object would be returned.
如果在本地存储库中找到了一个支持所需的显式接口的服务，将返回对该服务对象的直接引用。
Unfortunately, it is incompatible because at the metadata level every method on every interface has its own slot (which makes explicit interface implementations work).
不幸的是，此假设与实际不符，因为在元数据级别上位于每个接口上的每个方法都有各自的槽(slot)(这使得显式接口实现得以工作)。
Prefer using explicit interface implementation.
优先使用明确的接口实现。
Prefer using explicit interface implementation.
推荐使用显示的接口实现。
Describes guidelines for explicit interface implementations.
描述显式接口实现的准则。
This economical and pragmatic system has explicit interface, with simple operation.
本系统界面友好，操作简单，比较实用。
The following design guidelines help ensure that your library design USES explicit interface implementation only when appropriate.
下列设计准则有助于确保您的库设计仅在需要时使用显式接口实现。
The use of pure abstract C++ explicit interface classes worked against true service invocation transparency, because service clients on non-C++ systems required alternative interface definitions.
使用纯粹的抽象 C++显式接口类与真正的服务调用透明性是矛盾的，因为非 C++系统中的服务客户机需要备用的接口定义。
Explicit interface implementation also allows the programmer to implement two interfaces that have the same member names and give each interface member a separate implementation.
显式接口实现还允许程序员实现具有相同成员名称的两个接口，并为每个接口成员各提供一个实现。
Explicit interface implementation also allows the programmer to implement two interfaces that have the same member names and give each interface member a separate implementation.
显式接口实现还允许程序员实现具有相同成员名称的两个接口，并为每个接口成员各提供一个实现。
应用推荐