EPL includes various data types. Basically, all the Win32 data types are compatible with EPL data type. Please see the data type conversion- relationship that list below.
| Win32 Data Type | EPL Data Type |
|---|---|
| BOOL | Integer |
| BSTR | String |
| BYTE | Byte |
| COLORREF | Integer |
| DWORD | Integer |
| LONG | Integer |
| LPARAM | Integer |
| LPCSTR | String |
| LPSTR | String |
| LPCTSTR | String |
| LPTSTR | String |
| LPVOID | Integer |
| LRESULT | Integer |
| UINT | Integer |
| WNDPROC | FunctionAddress |
| WORD | Short |
| WPARAM | Integer |
To declare Windows APIs in EPL Application is quite a bit of different. First, you should know the data type conversion-relationship between EPL and Win32 C language (just see previous content). Basically EPL data type can simulate all basic data type of Win32, so you should not worry about some structural Windows-Defined data type, because all the structural data types is mixed by basic data types. You can add User-Defined data type to simulate the same type that defined in Win32. You can also add API declarations by some EPL APIs Tools.
Actually, Windows APIs are all provided in Dlls. Windows DLL chapter describes how to declare a Windows API in EPL