in reply to Win32::API passing a parameter by reference issue

My question to the monks is, why does this my $buffersize= \$wParam; allow my function to work for multiple scans.

If anything is surprising is that it worked the first time without it. The documentation clearly states the variable must contains the size of the allocated buffer when the function is called.

  • Comment on Re: Win32::API passing a parameter by reference issue

Replies are listed 'Best First'.
Re^2: Win32::API passing a parameter by reference issue
by rpnoble419 (Pilgrim) on Jun 22, 2008 at 12:36 UTC
    My example was not clear. I did try using $wParam as the buffer size as that is what was returned by the message hook from Win32::GUI. That still caused the system to hang on the second pass. It was not until I created the reference to wParam that it worked.

      I was experiencing this same issue of the function call only happening once and then the next time the script would just end. Though it looks like we might have been experiencing it for different reasons figured I would post my solution since this is the first google result I got, maybe someone else will find it helpful :)

      Anywise, I was defining my function like this:

      my $getIndivPages = new Win32::API('c:\WINNT\system32\ALISE_Domain_nav.dll', 'GetPageNum', 'PPPP', 'N');

      And it work work the first time I did $getInivPages->Call(...), however I had this in a loop to be executed n times and it would only be executed once. So after much frustration I tried a random thing and redefined my function like this:

      my $getIndivPages = Win32::API->new('c:\WINNT\system32\ALISE_Domain_nav.dll', 'void __stdcall GetPageNum(long num, char *con, char *tit, char *url)');

      And it worked! (though I couldn't believe that's what was wrong after wasting many hours), anywise going through the loop the function would be executed the intended amount of times. Seems weird for it to be able to work just by changing how the function is defined but whatever.