----- Original Message ----- From: "Bill Luebkert" <[EMAIL PROTECTED]> . . >> >> If the C++ docs are there, I'd probably be tempted to use Inline::CPP >> (which >> also requires a C++ compiler). > > It should also be easily accomplished using Win32::API or > Win32API::Prototype > if you have the function name, arg types, return value and DLL name (as > previously > suggested). You have to be careful with ptrs and return args is all.
Yes - I probably should have made it clearer that I was merely stating a personal preference. (Though, to be strictly accurate, I should say that I prefer to use Inline::C to Win32::API ... I haven't actually used Inline::CPP much at all :-) I should also have pointed out that for Inline::C/Inline::CPP you'll also need the relevant header (.h) files - and the import library (.lib), too (assuming you're using a Microsoft compiler). On the other side of the ledger, I think that Win32::API still requires that the dll has been built using __stdcall calling convention, whereas that's not a requirement with Inline::C/Inline::CPP. (Perhaps things have changed on that score. I think there's a version of Win32::API-0.20 around somewhere that supports __cdecl calling convention, and perhaps that has been extended to the latest version of Win32::API, too .... not sure.) One often finds that third party dll's use __cdecl calling convention. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
