Re: Non-COM funtions in DLLs
Robert Hastings <[email protected]>
| Newsgroups | gmane.comp.windows.devel.jawin |
|---|---|
| Message-ID | <002d01c460d4$ae845d60$5827e4d8@S0027304714> |
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 > > > > > > > >