Re: Non-COM funtions in DLLs

Cyril <[email protected]>
Newsgroups gmane.comp.windows.devel.jawin
Message-ID <000901c460ed$14f67bb0$0101c80a@home1kvb86k4sm>
My idea is that to investigate how VB call a static function with OLE
Automation SDK. Just now I have realized how to convert IUnknown
(oleautomation compatible) to IDispatch interface. The same could be done
with a static function.

Vitaly Shelest


----- Original Message -----
From: "Robert Hastings" <[email protected]>
Newsgroups: gmane.comp.windows.devel.jawin
Sent: Saturday, July 03, 2004 10:06 AM
Subject: Re: Non-COM funtions in DLLs


> Yes,
> jSegue should be able to support this. There's no documentation yet on
> how to do it, but if Maxym is interested he can post a request to the
jSegue
> help forum and I'll respond.
>
> Thanks,
> Robert
>
> ----- Original Message -----
> From: "Roger I Martin PhD" <[email protected]>
> To: <[email protected]>
> Sent: Friday, July 02, 2004 2:41 PM
> Subject: Re: [JAWIN] Non-COM funtions in DLLs
>
>
> > Interesting.  There is more info in the dll and entries than in a vendor
> > supplied header( with lib) file?  The reason I think about the header
and
> > lib file is that it is the vendor supplied interface to their software.
> The
> > question that gets raised is "Is it considered reverse engineering to go
> > into dlls to create an interface to them?  Might find some interesting
> > undocumented methods:-)
> >
> > --Roger
> > ----- Original Message -----
> > From: "Cyril" <[email protected]>
> > To: <[email protected]>
> > Sent: Friday, July 02, 2004 9:42 AM
> > Subject: Re: [JAWIN] Non-COM funtions in DLLs
> >
> >
> > > It is enough to construct a function prototype (for marshal) with Java
> > > Reflection. Remember, in MS VB you can declare a static function
> prototype
> > > (with DLL and an entry names) and VB ''knows" how to treat with it.
> > >
> > > Vitaly Shelest
> > >
> > > ----- Original Message -----
> > > From: "Roger I Martin PhD" <[email protected]>
> > > Newsgroups: gmane.comp.windows.devel.jawin
> > > Sent: Monday, June 28, 2004 3:28 PM
> > > Subject: Re: Non-COM funtions in DLLs
> > >
> > >
> > > > With some of the info coming from the user?...
> > > > ----- Original Message -----
> > > > From: "Robert Hastings" <[email protected]>
> > > > To: <[email protected]>
> > > > Sent: Sunday, June 27, 2004 4:20 PM
> > > > Subject: [JAWIN] Non-COM funtions in DLLs
> > > >
> > > >
> > > > > Instead of trying to parse the header files directly why don't we
> > build
> > > a
> > > > > typelibrary with a module section that describes all of the
> funtions.
> > > Then
> > > > > we can use the typelib browser to auto generate the calls. That
way
> > we'd
> > > > > have the necessary [in] [out] markers... Of course, we'd need to
> > enhance
> > > > the
> > > > > typelib browser to support modules/functions.
> > > > >
> > > > > Robert
> > > > >
> > > >
> >
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.