Текущий архив: 2002.01.08;
DLL S Найти похожие ветки← →
HELP ME PLZ (2001-12-15 18:22) 
ПОМОГИТЕ МНЕ ПОЖАЛУЙСТА Я ПЕРВЫЙ РАЗ РАБОТАЮ С DLL КАК ВЫЗВАЬ ФУНКЦИЮ ИЗ DLL-шки
Oleg Gashev (2001-12-15 18:35) 
Topic group See also
Before you can call routines defined in a DLL, you must import them. This can be done in two ways: by declaring an external procedure or function, or by calling the Windows API directly. Whichever method you use, the routines are not linked to your application until runtime. This means that the DLL need not be present when you compile your program. It also means that there is no compile-time validation of attempts to import a routine.
Object Pascal does not support importing of variables from DLLs.
The simplest way to import a procedure or function is to declare it using the external directive. For example,
procedure DoSomething; external "MYLIB.DLL";
If you include this declaration in a program, MYLIB.DLL is loaded once, when the program starts. Throughout execution of the program, the identifier DoSomething always refers to the same entry point in the same DLL.
Declarations of imported routines can be placed directly in the program or unit where they are called. To simplify maintenance, however, you can collect external declarations into a separate “import unit” that also contains any constants and types required for interfacing with the DLL. (Delphi’s Windows unit is a good example.) Other modules that use the import unit can call any routines declared in it.
For more information about external declarations, see External declarations .
Dynamic loading through Windows API calls.
Oleg Gashev (2001-12-15 18:36) 
The LoadLibrary function maps the specified executable module into the address space of the calling process.
LPCTSTR lpLibFileName // address of filename of executable module
Points to a null-terminated string that names the executable module (either a .DLL or .EXE file). The name specified is the filename of the module and is not related to the name stored in the library module itself, as specified by the LIBRARY keyword in the module-definition (.DEF) file.
If the string specifies a path but the file does not exist in the specified directory, the function fails.
If a path is not specified and the filename extension is omitted, the default library extension .DLL is appended. However, the filename string can include a trailing point character (.) to indicate that the module name has no extension. When no path is specified, the function searches for the file in the following sequence:
1. The directory from which the application loaded.
2. The current directory.
3. Windows 95: The Windows system directory. Use the GetSystemDirectory function to get the path of this directory.
Windows NT: The 32-bit Windows system directory. Use the GetSystemDirectory function to get the path of this directory. The name of this directory is SYSTEM32.
4. Windows NT: The 16-bit Windows system directory. There is no Win32 function that obtains the path of this directory, but it is searched. The name of this directory is SYSTEM.
5. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
6. The directories that are listed in the PATH environment variable.
The first directory searched is the one directory containing the image file used to create the calling process (for more information, see the CreateProcess function). Doing this allows private dynamic-link library (DLL) files associated with a process to be found without adding the process"s installed directory to the PATH environment variable.
Once the function obtains a fully qualified path to a library module file, the path is compared (case independently) to the full paths of library modules currently loaded into the calling process. These libraries include those loaded when the process was starting up as well as those previously loaded by LoadLibrary but not unloaded by FreeLibrary . If the path matches the path of an already loaded module, the function just increments the reference count for the module and returns the module handle for that library.
If the function succeeds, the return value is a handle to the module.
If the function fails, the return value is NULL. To get extended error information, call GetLastError .
LoadLibrary can be used to map a DLL module and return a handle that can be used in GetProcAddress to get the address of a DLL function. LoadLibrary can also be used to map other executable modules. For example, the function can specify an .EXE file to get a handle that can be used in FindResource or LoadResource .
Module handles are not global or inheritable. A call to LoadLibrary by one process does not produce a handle that another process can use
Страницы: 1 вся ветка
Текущий архив: 2002.01.08;
Память: 0.57 MB
Время: 0.048 c