但是有时也需要显式链接。
However, there are times when explicit linking is necessary.
有两种类型的链接：隐式链接和显式链接。
There are two types of linking: implicit linking and explicit linking.
显式链接有时称为动态加载或运行时动态链接。
Explicit linking is sometimes referred to as dynamic load or run-time dynamic linking.
在显式链接下，应用程序必须进行函数调用以在运行时显式加载DLL。
With explicit linking, applications must make a function call to explicitly load the DLL at run time.
将调用应用程序当时不需要的其他函数放在另一个DLL 中，并使应用程序显式链接到此 DLL。
Put the other functions that the calling application does not need right away into another DLL and have the application explicitly link to that DLL.
为提高启动性能，应用程序可隐式链接到那些加载后立即需要的DLL，并等到在需要时显式链接到其他DLL。
To improve startup performance, an application can implicitly link to those DLLs needed immediately after loading and wait to explicitly link to the other DLLs when they are needed.
在显式链接下，使用DLL的可执行文件必须进行函数调用以显式加载和卸载该DLL，并访问该DLL的导出函数。
With explicit linking, the executable using the DLL must make function calls to explicitly load and unload the DLL and to access the DLL's exported functions.
也请注意必须要显式指定链接寄存器。
Notice also that you have to specify the link register explicitly.
它们必须由某个显式的用户交互（通常是通过单击Portlet中的某个操作链接）发起，并且不能在第一次跳转到某个页面时将它们用于设置协作视图。
They must be initiated by some explicit user interaction (normally, by clicking an action link in a portlet), and they cannot be used to set up a coordinated view when first jumping to a page.
脚本仍然能够处理显式的注销请求，以及构建和返回正确的实例信息，因此个人页面上的链接还将有效。
The script can still handle explicit logout requests, and building and returning the appropriate instance information, so links on the individual pages will still work.
脚本仍然能够处理显式的注销请求，以及构建和返回正确的实例信息，因此个人页面上的链接还将有效。
The script can still handle explicit logout requests, and building and returning the appropriate instance information, so links on the individual pages will still work.
应用推荐