There is a bug in the prototype definition. The quickest solution is to patch the Win32::API module by 'voiding' the custom prototype.

...
my $f = Win32::API->new("winmm", "long mciSendString(LPSTR a, LPSTR b,
+ long c, long d)");

delete $f->{proto};
delete $f->{intypes};
...

[download]

This will force Win32::API to behave the same as
Win32::API->new("winmm", "PPNN", "N");

[download]


It is often useful to turn on the internal debugging of Win32::API to work out what is the prototype parser doing. Turn on debugging with $Win32::API::DEBUG = 1;. This shows that in your first prototype, the char * was interpreted as char. Win32::API was not doing a good job at parsing char *. (grin...)

In reply to Re: c style Win32::API interface by Roger
in thread c style Win32::API interface by pg

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.