Hello 

> > anything. What's worse, the pointers or references to the classes you are
> > passing back and forth could have different declared implementations on both
> > sides of the interface. CString (as an example) on one side could have a
> > method GetLength( ), and not have it in the header definition on the other
> > side. So what happens if the side without creates a CString object, passes
> > it across the interface boundary, and the guy on that side tries to call
> > GetLength( ) on it?
 
> but the headers *are* available ... so it should be deal-withable.
Headers  are not an issue here. What I am talking about is that things has 
different names in LIB/DLL. I can send you a LIB and HPP file of a simple 
class, with only static memeber, but you will not be able to use (you will 
fail at link time) even with headers available, since I won't tell you which 
compiler to use. But any functions, delclared as extern "C *will* be useful, 
since mangling (AKA decorating) is standard, although unofficial

-- 
--
Regards,
Waleri

Reply via email to