> So, I understand is that if one DLL (foo) calls another DLL (bar) then
> foo already has stubs for bar compiled in and I don't need to make
> stubs for bar if I don't want to call it directly from my WineLib
> program?
correct
> I am almost sure that my DLLs are compiled with MSVC++ 5.0 or 6.0.
> Are there any "demanglers" for MSVC++ such as c++filt in GNU C++? Or
> maybe someone knows a place with documentation of MSVC++ object layout
> and virtual methods handling?
hae you tried msdn ? a pedump on the dll shall also give out the list
of exported functions, someone sent me long ago a MSVC++ demangler but
i can't put myhands on it
> I am considering using Borland tools to compile a small program which
> could be ran in wine. How much of performance I would loose doing
> things in that way?
compared to which way ?
> The vendor also supplied an OLE control as an interface to the dlls.
> What if I wanted to use OLE automation in WineLib to get things
> working? Do you happen to know what part of Wine source code tree
> covers ActiveX controls?
check out the dlls/*ole* subdirs, but automation is not yet finished
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
