Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _4b4ecaf6c70a9b0d2ef1ea0d577c27ff < prev next >

Wrap

Text File | 2000-03-23 | 12.9 KB | 295 lines

<HTML> <HEAD> <TITLE>Win32::API - Implementation of arbitrary Win32 APIs.</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Win32::API - Implementation of arbitrary Win32 APIs. </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#abstract">ABSTRACT</A></LI> <LI><A HREF="#credits">CREDITS</A></LI> <LI><A HREF="#installation">INSTALLATION</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <UL> <LI><A HREF="#importing a function">IMPORTING A FUNCTION</A></LI> <LI><A HREF="#calling an imported function">CALLING AN IMPORTED FUNCTION</A></LI> </UL> <LI><A HREF="#author">AUTHOR</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> Win32::API - Implementation of arbitrary Win32 APIs. <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> <PRE> use Win32::API; $function = new Win32::API($library, $functionname, \@argumenttypes, $returntype); $return = $function->Call(@arguments);</PRE> <HR> <H1><A NAME="abstract">ABSTRACT</A></H1> With this module you can import and call arbitrary functions from Win32's Dynamic Link Libraries (DLL). The current version of Win32::API is available at: <PRE> <A HREF="http://www.divinf.it/dada/perl/api/">http://www.divinf.it/dada/perl/api/</A></PRE> It is also available on your nearest CPAN mirror (but allow a few days for worldwide spreading of the latest version) reachable at: <PRE> <A HREF="http://www.perl.com/CPAN/authors/Aldo_Calpini/">http://www.perl.com/CPAN/authors/Aldo_Calpini/</A></PRE> <HR> <H1><A NAME="credits">CREDITS</A></H1> All the credits go to Andrea Frosini ( <A HREF="mailto:frosini@programmers.net">frosini@programmers.net</A> ), for his bits of magic - eg. the assembler trick that make this thing work. A big thank you also to Gurusamy Sarathy ( <A HREF="mailto:gsar@engin.umich.edu">gsar@engin.umich.edu</A> ) for his help in XS development <CODE>:)</CODE> <HR> <H1><A NAME="installation">INSTALLATION</A></H1> This module comes with pre-built binaries for: <DL> <DT><A NAME="item_higher">The Perl for Win32 port by ActiveWare: Build 300 or higher (EXCEPT 304!)</A> <DD> <DT><A NAME="item_The_core_Perl_5%2E004_distribution%3A_Built_on_the">The core Perl 5.004 distribution: Built on the Win32 platform, of course...</A> <DD> </DL> To install the package, just change to the directory in which you uncompressed it and type the following: <PRE> install</PRE> This will take care of copying the right files to the right places for use by all your perl scripts. If you're running the core Perl 5.004 distribution, you can also build the extension by yourself with the following procedure: <PRE> perl Makefile.PL nmake nmake install</PRE> If you are instead running the ActiveWare Perl for Win32 port, the sources to rebuild the extension are in the ActiveWare/source directory. You should put those files in the following directory: <PRE> (perl-src)\ext\Win32\API</PRE> Where <CODE>(perl-src)</CODE> is the location of your Perl-Win32 source files. <HR> <H1><A NAME="description">DESCRIPTION</A></H1> To use this module put the following line at the beginning of your script: <PRE> use Win32::API;</PRE> You can now use the <CODE>new()</CODE> function of the Win32::API module to create a new API object (see <A HREF="#importing a function">IMPORTING A FUNCTION</A>) and then invoke the <CODE>Call()</CODE> method on this object to perform a call to the imported API (see <A HREF="#calling an imported function">CALLING AN IMPORTED FUNCTION</A>). <H2><A NAME="importing a function">IMPORTING A FUNCTION</A></H2> You can import a function from a Dynamic Link Library (DLL) file with the <CODE>new()</CODE> function. This will create a Perl object that contains the reference to that function, which you can later Call(). You need to pass 4 parameters: <OL> <LI><A NAME="item_The_name_of_the_library_from_which_you_want_to_imp">The name of the library from which you want to import the function.</A> <LI><A NAME="item_function">The name of the function (as exported by the library).</A> <LI><A NAME="item_The_number_and_types_of_the_arguments_the_function">The number and types of the arguments the function expects as input.</A> <LI><A NAME="item_The_type_of_the_value_returned_by_the_function%2E">The type of the value returned by the function.</A> </OL> To explain better their meaning, let's make an example: I want to import and call the Win32 API <CODE>GetTempPath()</CODE>. This function is defined in C as: <PRE> DWORD WINAPI GetTempPathA( DWORD nBufferLength, LPSTR lpBuffer );</PRE> This is documented in the Win32 SDK Reference; look for it on the Microsoft's WWW site. If you own Visual C++, searching in the include files is much faster. 1. The first parameter is the name of the library file that exports this function; our function resides in the KERNEL32.DLL system file. When specifying this name as parameter, the .dll extension is implicit, and if no path is given, the file is searched through the Windows directories. So I don't have to write C:\windows\system\kernel32.dll; only kernel32 is enough: <PRE> $GetTempPath = new Win32::API("kernel32", ...</PRE> 2. Now for the second parameter: the name of the function. It must be written exactly as it is exported by the library (case is significant here). If you are using Windows 95 or NT 4.0, you can use the Quick View command on the DLL file to see the function it exports. Note that many Win32 APIs are exported twice, with the addition of a final A or W to their name, for - respectively - the ASCII and the Unicode version. Win32::API, when a function name is not found, will actually append an A to the name and try again. If you are using Unicode, you will just need to rebuild the module; then Win32::API will try with the W. So my function name will be: <PRE> $GetTempPath = new Win32::API("kernel32", "GetTempPath", ...</PRE> Note that <CODE>GetTempPath</CODE> is really loaded as <CODE>GetTempPathA</CODE>. 3. The third parameter, the input parameter list, specifies how many arguments the function wants, and their types. It MUST be passed as a list reference. The following forms are valid: <PRE> [a, b, c, d] \@LIST</PRE> But those are not: <PRE> (a, b, c, d) @LIST</PRE> The number of elements in the list specifies the number of parameters, and each element in the list specifies the type of an argument; allowed types are: <DL> <DT><A NAME="item_I%3A_value_is_an_integer"><CODE>I</CODE>: value is an integer</A> <DD> <DT><A NAME="item_number"><CODE>N</CODE>: value is a number (long)</A> <DD> <DT><A NAME="item_pointer"><CODE>P</CODE>: value is a pointer (to a string, structure, etc...)</A> <DD> </DL> Our function needs two parameters: a number (<CODE>DWORD</CODE>) and a pointer to a string (<CODE>LPSTR</CODE>): <PRE> $GetTempPath = new Win32::API("kernel32", "GetTempPath", [N, P], ...</PRE> 4. The fourth and final parameter is the type of the value returned by the function. It can be one of the types seen above, plus another type named V (that stands for <A HREF="../../../lib/Pod/perlguts.html#item_void"><CODE>void</CODE></A>) to indicate that the function doesn't return a value. In our example the value returned by <CODE>GetTempPath()</CODE> is a <CODE>DWORD</CODE>, so our return type will be N: <PRE> $GetTempPath = new Win32::API("kernel32", "GetTempPath", [N, P], N);</PRE> Now the line is complete, and the API <CODE>GetTempPath()</CODE> is available for use in Perl. Before you can call it, you should test that $GetTempPath is <A HREF="../../../lib/Pod/perlfunc.html#item_defined"><CODE>defined</CODE></A>, otherwise either the function or the library has not been found. <H2><A NAME="calling an imported function">CALLING AN IMPORTED FUNCTION</A></H2> To effectively make a call to an imported function you must use the <CODE>Call()</CODE> method on the Win32::API object you created. To continue with the example from the previous paragraph, I can call the <CODE>GetTempPath()</CODE> API via the method: <PRE> $GetTempPath->Call(...</PRE> Of course I have to pass the parameters as defined in the import phase. In particular, if the number of parameters does not match (in the example, if I call <CODE>GetTempPath()</CODE> with more or less than two parameters), Perl will <CODE>croak</CODE> an error message and <A HREF="../../../lib/Pod/perlfunc.html#item_die"><CODE>die</CODE></A>. So I need two parameters here: the first is the length of the buffer that will hold the returned temporary path, the second is the buffer itself. For numerical parameters you can use either a constant expression or a variable, while for pointers you must use a variable name (no reference, just a plain variable name). Also note that memory must be allocated before calling the function. For example, if I want to pass a buffer of 80 characters to GetTempPath(), I have to initialize it before with: <PRE> $lpBuffer = " " x 80;</PRE> This allocates a string of 80 characters. If you don't do so, you'll probably get '<CODE>Runtime exception</CODE>' errors, and generally nothing will work. My call should therefore include: <PRE> $lpBuffer = " " x 80; $GetTempPath->Call(80, $lpBuffer);</PRE> And the result will be stored in the $lpBuffer variable. Note, however, that Perl does not trim the variable, so $lpBuffer will contain 80 characters in return; the exceeding characters will be spaces, since I initialized the variable with <CODE>" " x 80</CODE>. In this case I'm lucky enough, because the value returned by the <CODE>GetTempPath()</CODE> function is the length of the string, so to get the actual temporary path I write: <PRE> $lpBuffer = " " x 80; $return = $GetTempPath->Call(80, $lpBuffer); $TempPath = substr($lpBuffer, 0, $return);</PRE> If you don't know the length of the string, you can usually cut it at the \0 (ASCII zero) character, which is the string delimiter in C: <PRE> $TempPath = ((split(/\0/, $lpBuffer))[0]; </PRE> <PRE> # or</PRE> <PRE> $lpBuffer =~ s/\0.*$//; $TempPath = $lpBuffer;</PRE> Another note: to pass a pointer to a structure in C, you'll have to <A HREF="../../../lib/Pod/perlfunc.html#item_pack"><CODE>pack()</CODE></A> the required elements in a variable. And of course, to access the values stored in a structure, <A HREF="../../../lib/Pod/perlfunc.html#item_unpack"><CODE>unpack()</CODE></A> it as required. An example of how it works: we have the <CODE>POINT</CODE> structure defined in C as: <PRE> typedef struct { LONG x; LONG y; } POINT;</PRE> Thus, to call a function that uses a <CODE>POINT</CODE> structure you will need the following lines: <PRE> $GetCursorPos = new Win32::API("user32", "GetCursorPos", [P], V); </PRE> <PRE> $lpPoint = pack("LL", 0, 0); # store two LONGs $GetCursorPos->Call($lpPoint); ($x, $y) = unpack("LL", $lpPoint); # get the actual values</PRE> The rest is left as an exercise to the reader... <HR> <H1><A NAME="author">AUTHOR</A></H1> Aldo Calpini ( <A HREF="mailto:dada@divinf.it">dada@divinf.it</A> ). <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Win32::API - Implementation of arbitrary Win32 APIs. </TD></TR> </TABLE> </BODY> </HTML>