Path: | doc.ic.ac.uk!dds |
From: | dds@doc.ic.ac.uk (Diomidis Spinellis) |
Newsgroups: | comp.lang.perl |
Subject: | Re: Perl's goodies in a Windows DLL |
Date: | 24 Nov 1993 12:20:31 GMT |
Organization: | Dept of Computing, Imperial College, England |
Lines: | 20 |
Distribution: | world |
Message-ID: | <2cvjif$ap1@frigate.doc.ic.ac.uk> |
References: | <wmeahan.15.2CEA381A@ef0424.efhd.ford.com> <2cl9i1$8b4@frigate.doc.ic.ac.uk> <2ctf2r$bqp@b11.b11.ingr.com> |
NNTP-Posting-Host: | scorch.doc.ic.ac.uk |
Content-Length: | 1174 |
In article <2ctf2r$bqp@b11.b11.ingr.com> clark@clark.b11.ingr.com (Clark Williams) writes:
>I've been planning to add some sort of "attach to DLL" and "call DLL
>function named 'foo'" to NT Perl, but haven't had the time. It seems like a
>trivial matter to add a usersub to load a DLL and return a handle for use from
>a perl script. It also seems doable to be able to add a routine that accepts a
>handle to a previously loaded DLL and a string representing a routine from the
>DLL to call. What I haven't figured out yet is a good generic way to indicate
>the types of the parameters to pass to the DLL routine.
I used pack and a knowledge of the C calling interface. It is hacky, and
not very friendly, but works. I presume one could write a more friendly
interface that uses the types of the Windows data types, and caches them
to a pack specification.
I found that the real problem is the absence of a good way to simplify
Windows programming using Perl (i.e. a GUI builder).
Diomidis
--
Diomidis Spinellis Internet: <dds@doc.ic.ac.uk> UUCP: ...!uknet!icdoc!dds
Department of Computing, Imperial College, London SW7 #include "/dev/tty"
Newsgroup comp.lang.perl contents
Newsgroup list
Diomidis Spinellis home page
Unless otherwise expressly stated, all original material on this page created by Diomidis Spinellis is licensed under a Creative Commons Attribution-Share Alike 3.0 Greece License.