Re: On runtimes, string wrapping and vs7 / vs8
Getting rid of your inline functions, and this includes any potentially
compiler-generated functions like default ctor, copy ctor, dtor, and
assignment operator, may indeed help, but the end result will remain a
problem waiting to happen. The only sane way to view this situation is as
the equivalent to working with static libraries for dependency purposes.
--
Doug Harrison
Visual C++ MVP
So now I know. Thank you for the answer Doug!
It seems as we have to go back to cons char* etc. What a shame.
Is there a (standard) way of handling strings (and other containers) in
libraries, or is the standard still the old c way of doing things since
c++ still haven't got a standard abi?
If you want your dlls to be portable across compilers, you have very little
choices.
Only char* or wchar_t* is portable
See my article about this:
http://vcfaq.mvps.org/lang/9.htm
--
Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"