🚀 go-pugleaf

>First of all the contents of 'Proc' are irrelevant at compile time because
>at compile time the variable doesn't even exist. That's the difference
>between 'compile time' and 'run time' :)

that makes sense now. thanks


>Thirdly:what's with the brackets? Are they really in the example?

yes, and i thought that was weird too, but i don't know any 
better since it is my first time working with run-time linking.





>> >What is MYPROC declared as exactly?  Chances are, it is not declared
>> >correctly.  
>> 
>> it is declared like this:
>> 
>> typedef VOID (*MYPROC)(LPTSTR);
>
>Now this is immediately a mismatch. This declares a pointer to a function
>that takes one argument. Unfortunately you've never given us the
>declaration of 'Proc' itself but if you have:
>
>MYPROC Proc;
>
>Then you've declared 'Proc' as pointing to a function that only takes one
>argument.
>
>What you need is:
>
>typdef VOID (*MYPROC)( ???, LPTSTR );
>
>Where '???' is the type of 'szRunTypes'.
>-- 
>Andrue Cope
>[Bicester UK]

that all made perfect sense once I heard it spelled out like that.
 I changed my definition of MYPROC to this:
typedef int (*MYPROC)(LPTSTR ,LPTSTR);
since both parameters are of type 'char *' However, now I am now
 getting this error:
[C++ Error] nycdsur040.cpp(7267): E2034 Cannot convert 'int (__stdcall *)()' to 'int (*)(char *,char *)'
it acts as though it has the function declared already.