I've never heard of "optional" arguments to a C routine. A variable number as with int printf( char *t, ... ), but not optional.
If you're going to access a vararg function using Win32::API, you would need to do something hinky like create one API mapping for each number of args you are likely to use and then call the appropriate variant:
use Win32::API;
$function2 = Win32::API->new(
'mydll', 'sum_integers', 'II', 'I',
);
$function3 = Win32::API->new(
'mydll', 'sum_integers', 'III', 'I',
);
$function4 = Win32::API->new(
'mydll', 'sum_integers', 'IIII', 'I',
);
$function5 = Win32::API->new(
'mydll', 'sum_integers', 'IIIII', 'I',
);
$function6 = Win32::API->new(
'mydll', 'sum_integers', 'IIIIII', 'I',
);
Not pretty, but it ought to at least work.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.