1、精選優質文檔-傾情為你奉上畢業設計（論文）外文文獻翻譯（本科學生用）題 目：_項目管理系統的設計與實現_ _學 生 姓 名：_ _學號：學 部 （系）: _專 業 年 級: _指 導 教 師：_ _ 職稱或學位： 2010 年 2 月 15 日 外文文獻翻譯：Library BasicsA Windows program is an executable file that generally creates one or more windows and uses a message loop to receive user input. Dynamic-link libraries are

2、 generally not directly executable, and they generally do not receive messages. They are separate files containing functions that can be called by programs and other DLLs to perform certain jobs. A dynamic-link library is brought into action only when another module calls one of the functions in the

3、 library. The term "dynamic linking" refers to the process that Windows uses to link a function call in one module to the actual function in the library module. "Static linking" occurs during program development when you link various object (.OBJ) modules, run-time library (.LIB)

4、 files, and usually a compiled resource (.RES) file to create a Windows .EXE file. Dynamic linking instead occurs at run time. KERNEL32.DLL, USER32.DLL, and GDI32.DLL; the various driver files such as KEYBOARD.DRV, SYSTEM.DRV, and MOUSE.DRV; and the video and printer drivers are all dynamic-link lib

5、raries. These are libraries that all Windows programs can use. Some dynamic-link libraries (such as font files) are termed "resource-only." They contain only data (usually in the form of resources) and no code. Thus, one purpose of dynamic-link libraries is to provide functions and resourc

6、es that can be used by many different programs. In a conventional operating system, only the operating system itself contains routines that other programs can call on to do a job. In Windows, the process of one module calling a function in another module is generalized. In effect, by writing a dynam

7、ic-link library, you are writing an extension to Windows. Or you can think of DLLs, including those that make up Windows, as extensions to your program. Although a dynamic-link library module can have any extension (such as .EXE or .FON), the standard extension is .DLL. Only dynamic-link libraries w

8、ith the extension .DLL will be loaded automatically by Windows. If the file has another extension, the program must explicitly load the module by using the LoadLibrary or LoadLibraryEx function. You'll generally find that dynamic libraries make most sense in the context of a large application. F

9、or instance, suppose you write a large accounting package for Windows that consists of several different programs. You'll probably find that these programs use many common routines. You could put these common routines in a normal object library (with the extension .LIB) and add them to each of t

10、he program modules during static linking with LINK. But this approach is wasteful, because each of the programs in this package contains identical code for the common routines. Moreover, if you change one of the routines in this library, you'll have to relink all the programs that use the change

11、d routine. If, however, you put these common routines in a dynamic-link library called, for instance, ACCOUNT.DLL, you've solved both problems. Only the library module need contain the routines required by all the programs, thus requiring less disk space for the files and less memory space when

12、running two or more of the applications simultaneously, and you can make changes to the library module without relinking any of the individual programs. Dynamic-link libraries can themselves be viable products. For instance, suppose you write a collection of three-dimensional drawing routines and pu

13、t them in a DLL called GDI3.DLL. If you then interest other software developers in using your library, you can license it to be included with their graphics programs. A user who has several of these programs would need only one GDI3.DLL file. Library: One Word, Many MeaningsPart of the confusion sur

14、rounding dynamic-link libraries results from the appearance of the word "library" in several different contexts. Besides dynamic-link libraries, we'll also be talking about "object libraries" and "import libraries." An object library is a file with the extension .LI

15、B containing code that is added to your program's .EXE file in the process called static linking when you run the linker. For example, in Microsoft Visual C+, the normal C run-time object library that you link with your program is called LIBC.LIB. An import library is a special form of an object

16、 library file. Like object libraries, import libraries have the extension .LIB and are used by the linker to resolve function calls in your source code. However, import libraries contain no code. Instead, they provide the linker with information necessary to set up relocation tables within the .EXE

17、file for dynamic linking. The KERNEL32.LIB, USER32.LIB, and GDI32.LIB files included with the Microsoft compiler are import libraries for Windows functions. If you call the Rectangle function in a program, GDI32.LIB tells LINK that this function is in the GDI32.DLL dynamic-link library. This informa

18、tion goes into the .EXE file so that Windows can perform dynamic linking with the GDI32.DLL dynamic-link library when your program is executed. Object libraries and import libraries are used only during program development. Dynamic-link libraries are used during run time. A dynamic library must be p

19、resent on the disk when a program is run that uses the library. When Windows needs to load a DLL module before running a program that requires it, the library file must be stored in the directory containing the .EXE program, the current directory, the Windows system directory, the Windows directory,

20、 or a directory accessible through the PATH string in the MS-DOS environment. (The directories are searched in that order.) 動態鏈接庫的基本知識Windows應用程序是一個可執行文件，它通常建立一個或幾個窗口，并使用消息循環接收使用者輸入。通常，動態鏈接庫并不能直接執行，也不接收消息。它們是一些獨立的文件，其中包含能被程序或其它DLL呼叫來完成一定作業的函數。只有在其它模塊呼叫動態鏈接庫中的函數時，它才發揮作用。所謂動態鏈接，是指Windows把一個模塊中的函數呼叫連結到

21、動態鏈接庫模塊中的實際函數上的程序。在程序開發中，您將各種目標模塊(.OBJ)、執行時期鏈接庫(.LIB)文件，以及經常是已編譯的資源(.RES)文件連結在一起，以便建立Windows的.EXE文件，這時的連結是靜態連結。動態鏈接與此不同，它發生在執行時期。KERNEL32.DLL、USER32.DLL和GDI32.DLL、各種驅動程序文件如KEYBOARD.DRV、SYSTEM.DRV和MOUSE.DRV和視訊及打印機驅動程序都是動態鏈接庫。這些動態鏈接庫能被所有Windows應用程序使用。有些動態鏈接庫（如字體文件等）被稱為純資源。它們只包含數據（通常是資源的形式）而不包含程序代碼。由此可

22、見，動態鏈接庫的目的之一就是提供能被許多不同的應用程序所使用的函數和資源。在一般的操作系統中，只有操作系統本身才包含其它應用程序能夠呼叫來完成某一作業的例程。在Windows中，一個模塊呼叫另一個模塊函數的程序被推廣了。結果使得編寫一個動態鏈接庫，也就是在擴充Windows。當然，也可認為動態鏈接庫（包括構成Windows的那些動態鏈接庫例程）是對使用者程序的擴充。盡管一個動態鏈接庫模塊可能有其它擴展名（如.EXE或.FON），但標準擴展名是.DLL。只有帶.DLL擴展名的動態鏈接庫才能被Windows自動加載。如果文件有其它擴展名，則程序必須另外使用LoadLibrary或者LoadLibr

23、aryEx函數加載該模塊。您通常會發現，動態鏈接庫在大型應用程序中最有意義。例如，假設要為Windows編寫一個由幾個不同的程序組成的大型財務軟件包，就會發現這些應用程序會使用許多共同的例程。可以把這些公共例程放入一個一般性的目的碼鏈接庫（帶.LIB擴展名）中，并在使用LINK靜態連結時把它們加入各程序模塊中。但這種方法是很浪費的，因為軟件包中的每個程序都包含與公共例程相同的程序代碼。而且，如果修改了鏈接庫中的某個例程，就要重新連結使用此例程的所有程序。然而，如果把這些公共例程放到稱為ACCOUNT.DLL的動態鏈接庫中，就可解決這兩個問題。只有動態鏈接庫模塊才包含所有程序都要用到的例程。這樣能為儲存文件節省磁盤空間，并且在同時執行多個應用程序時節省內存，而且，可以修改動態鏈接庫模塊而不用重新連結各個程序。動態鏈接庫實際上是可以獨立存在的。例如，假設您編寫了一系列3D繪圖例程，并把它們放入名為GDI3.DLL的DLL中。如果其它軟件開發者對此鏈接庫很感興趣，您就可以授權他們將其加入他們的圖形程序中。使用多個這樣的圖形程序的使用者只需要一個GDI3.DLL文件。鏈接庫：一詞多義動態鏈接庫有著令人困惑的印象，部分原因是由于鏈接