Semiconductor & Computer Engineering
From WikiChip
Difference between revisions of "mirc/dynamic-link library"
m (added Category:MIRC using HotCat) |
(→Prototype) |
||
| Line 1: | Line 1: | ||
| + | The /dll and $dll() features allow you to make calls to DLLs designed to work with mIRC. The main reason you would want to do this is that processing information in a DLL can be far faster than doing so in a script, so for intensive data processing a DLL would be more efficient. | ||
| + | |||
| + | '''Note''': mIRC also supports calling {{mIRC|Component Object Model (COM)|COM}} objects, for calling non-standard DLLs. | ||
| + | |||
| + | |||
| + | |||
== Prototype == | == Prototype == | ||
The exported function must have the following function prototype: | The exported function must have the following function prototype: | ||
Revision as of 11:56, 20 July 2014
The /dll and $dll() features allow you to make calls to DLLs designed to work with mIRC. The main reason you would want to do this is that processing information in a DLL can be far faster than doing so in a script, so for intensive data processing a DLL would be more efficient.
Note: mIRC also supports calling COM objects, for calling non-standard DLLs.
Prototype
The exported function must have the following function prototype:
#include <windows.h>
int funcName(HWND mWnd, HWND aWnd, char *data, char *parms, BOOL show, BOOL nopause);
Note: These functions must use the stdcall calling convention. (This is also the standard calling convention for all other Microsoft Win32 API functions.)