: Jan Dubois
Cc: Perl-Win32-Users@listserv.ActiveState.com
Subject: RE: More on Re: Windows DLL - Perl Interface
Update, the WS_FTP object model doesn't mention the IDispatch interface
but I sent an email to a tech to answer. I guess I could put code
together and see if it works but I would wa
On Mon, 04 Apr 2005, Bharucha, Nikhil wrote:
> I looked at OLE quickly before and I looked at it again -- see you
> worked on it too!
Yeah, I wrote probably 90% of the code in Win32::OLE. :)
> I am trying to access the WS_FTP API. This is done
> by accessing the WsftpApi interfa
rface.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Bharucha, Nikhil
Sent: Monday, April 04, 2005 11:33 AM
To: Jan Dubois
Cc: Perl-Win32-Users@listserv.ActiveState.com
Subject: RE: More on Re: Windows DLL - Perl Interface
Jan,
I looked at OLE quickly before
Message-
From: Jan Dubois [mailto:[EMAIL PROTECTED]
Sent: Monday, April 04, 2005 11:09 AM
To: Bharucha, Nikhil; Perl-Win32-Users@listserv.ActiveState.com
Subject: RE: More on Re: Windows DLL - Perl Interface
On Mon, 04 Apr 2005, Bharucha, Nikhil wrote:
> Does anyone have any other ideas
On Mon, 04 Apr 2005, Bharucha, Nikhil wrote:
> Does anyone have any other ideas of attacking this problem of
> accessing a COM object in a DLL from Win32 Perl?
It depends on the COM object. If it implements IDispatch then you
could use Win32::OLE to access it.
Cheers,
-Jan
e: Windows DLL - Perl Interface
- Original Message -
From: "Johan Lindström" <[EMAIL PROTECTED]>
To:
Sent: Friday, April 01, 2005 8:24 AM
Subject: RE: More on Re: Windows DLL - Perl Interface
> At 23:41 2005-03-31, Lloyd Sartor wrote:
> >But if I needed a s
r [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 31, 2005 4:42 PM
To: Bharucha, Nikhil
Cc: Sisyphus; Perl-Win32-Users@listserv.ActiveState.com;
[EMAIL PROTECTED]
Subject: RE: More on Re: Windows DLL - Perl Interface
It's not clear to me what is meant by "an OO manner." Is the DLL an
- Original Message -
From: "Johan Lindström" <[EMAIL PROTECTED]>
To:
Sent: Friday, April 01, 2005 8:24 AM
Subject: RE: More on Re: Windows DLL - Perl Interface
> At 23:41 2005-03-31, Lloyd Sartor wrote:
> >But if I needed a solution in a timely manner,
At 23:41 2005-03-31, Lloyd Sartor wrote:
But if I needed a solution in a timely manner, I would concisely define
what must be OO, and then probably attack it with Inline::C or Inline:C++.
Win32::API certainly has its limitations.
That's a good idea, except Inline::CPP doesn't work very well on Wi
- Original Message -
From: "Lloyd Sartor" <[EMAIL PROTECTED]>
To: "Bharucha, Nikhil" <[EMAIL PROTECTED]>
Cc: "Sisyphus" <[EMAIL PROTECTED]>;
;
<[EMAIL PROTECTED]>
Sent: Friday, April 01, 2005 7:41 AM
Subject: RE: More on Re: Windows
isyphus
> Sent: Tuesday, March 15, 2005 4:03 PM
> Cc: Perl-Win32-Users@listserv.ActiveState.com
> Subject: Re: More on Re: Windows DLL - Perl Interface
>
> Lloyd Sartor wrote:
> > FYI - if I had to do it all over again, I would go the Inline::C
> route,
> > although it ma
...
Isn't there something easier to use out there?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sisyphus
Sent: Tuesday, March 15, 2005 4:03 PM
Cc: Perl-Win32-Users@listserv.ActiveState.com
Subject: Re: More on Re: Windows DLL - Perl Interface
Lloyd Sartor wrote:
FYI - if I had to do it all over again, I would go the Inline::C route,
although it may take some time to get the compiler tools installed.
That's my preferred route, too - and installing the "compiler tools"
amounts to nothing more than installing the MinGW binaries (and als
13 matches
Mail list logo
