说它不是完整的，是因为它仅仅包含了契约的静态部分，让服务器在运行时通过链接描述可能的工作流。
It is not complete since it just includes the static aspects of the contract, leaving the server to describe the possible workflow at runtime via links.
换句话说，链接以一种运行时工作流的形式动态地描述了客户端和服务器之间的契约。
In other words, links dynamically describe the contract between the client and the server in the form of a workflow at runtime.
与大内存模型类似，可以通过一个链接器选项或在运行时使用LDR_CNTRL环境变量来为编译时的可执行程序启用超大内存模型。
The very large memory model, like the large memory model, can be enabled for an executable at compile time with a linker option or at run time using the LDR_CNTRL environment variable.
要将其链接到可执行程序中，需要启用编译时链接器和运行时动态链接器来定位它。
To link this into executables, you need to enable both the compile-time linker and the run-time dynamic linker to find it.
包括无障碍访问支持、运行时本地化，以及内建的深度链接支持(浏览器后退、书签等等)。
These include improvements to accessibility, runtime localization, and built-in deep linking support (browser back, bookmarking, etc).
在RESTful应用中，服务器在运行时以链接形式提供这个信息。
In RESTful applications, servers provide this information at runtime in the form of links.
这个服务器 运行时，要能够通过使用RationalTeam Concert客户端来链接到服务器。
The server needs to be running to be able to connect to the server by using the Rational Team Concert client.
真正错误在于，编译器需要一个单独的标记来告诉它 /usr/X11R6/lib 需要在搜索目录列表中出现，这样在运行时才可以找到动态链接库。
What really went wrong is that the compiler needed a separate flag to tell it that /usr/X11R6/lib needed to be in the list of directories to search at runtime for dynamically-linked libraries.
为什么声明为模板实例化运行时多态导致链接器错误呢？
Why does declaring runtime polymorphism for template instantiations result in linker error?
为什么声明为模板实例化运行时多态导致链接器错误呢？
Why does declaring runtime polymorphism for template instantiations result in linker error?
应用推荐