Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: adebaene@xxxxxxxxxxxxxxxx
- Date: Wed, 17 Oct 2007 05:39:33 -0700
On Oct 16, 6:29 pm, "Ben Voigt [C++ MVP]" <r...@xxxxxxxxxxxxx> wrote:
Well, exposing a pure interface also gives binary compatibility while
preserving OO style. But those are essentially the three options for
reusable C++ libraries.
Except that the pure interface cannot use library objects in it's
definition (eg, you can't have a method that take a std::string as
parameter in your pure interface). This makes this approach not very
much better that a C-style interface, because you'are doomed to define
all types used in the interface - or use "compatible" types like the
ugly BSTR and it's awfull API.
Arnaud
.
- References:
- passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Creativ
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: David Wilkinson
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Ben Voigt [C++ MVP]
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Mihai N.
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Ben Voigt [C++ MVP]
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Mihai N.
- Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- From: Ben Voigt [C++ MVP]
- passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- Prev by Date: Re: VS2005 : Managed Wrapper for Unmanaged code : Ellipsis dilema
- Next by Date: Re: VS2005 : Managed Wrapper for Unmanaged code : Ellipsis dilema
- Previous by thread: Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- Next by thread: Re: passing std::string from visual studio 2005 to an C++ DLL generated by VC 6.0
- Index(es):