- Aug
- 29
- 0
I'm trying to use either @WINAPI or @CAPI to execute a function in a DLL. I've written C++ code that can use the DLL, so I know the name of the function(s), and I know the DLL is working/functional.
The prototype for the function(s) I'm wishing to "wrap" are:
LPCSTR (CALLBACK* LPFNDLLFUNC)(LPCSTR)
The function names are "Encrypt" and "Decrypt".
As near as I can tell, the correct use of either variable function is something like:
echo %@xAPI[mydll.dll,Encrypt,aBUFFER,"plaintext"] (where xAPI is either WIN or C)
and it should return the text value that is the string being pointed to by the function's return value. However, in practice, nothing is returned, so I know that I'm missing something.
Can anyone shed some light on what I'm missing? I'd really like to be able to use this...
The prototype for the function(s) I'm wishing to "wrap" are:
LPCSTR (CALLBACK* LPFNDLLFUNC)(LPCSTR)
The function names are "Encrypt" and "Decrypt".
As near as I can tell, the correct use of either variable function is something like:
echo %@xAPI[mydll.dll,Encrypt,aBUFFER,"plaintext"] (where xAPI is either WIN or C)
and it should return the text value that is the string being pointed to by the function's return value. However, in practice, nothing is returned, so I know that I'm missing something.
Can anyone shed some light on what I'm missing? I'd really like to be able to use this...