Win32::API treats the "P" prototype as "any" pointer - it is opaque to Win32::API and you need to post-process the value with pack>/tt> and unpack. This is not as nice as it could be, but as you are interfacing with C-level subroutines anyway, some knowledge about the stuff is needed anyway. You might have success by using the C-prototype version of Win32::API, that tries to interpret the C-prototypes of functions, but then you would need to find a way to tell Win32::API what a hFOO is without Win32::API having access to the relevant include and header files. See Convert::Binary::C for a module that does this task, and also for how ugly that way is, as Convert::Binary::C needs to implement its own C preprocessor for tracing the include statements of header files.

In reply to Re^5: Passing/Returning HANDLE's with Win32::API by Corion
in thread Passing/Returning HANDLE's with Win32::API by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.