Boost logo

Boost :

From: Carl Daniel (cpdaniel_at_[hidden])
Date: 2002-10-20 18:16:19


"Edward Diener" <eddielee_at_[hidden]> wrote in message
news:aovcam$m9u$1_at_main.gmane.org...
> "Carl Daniel" <cpdaniel_at_[hidden]> wrote in message
> news:aov8il$qoq$1_at_main.gmane.org...
> > "Edward Diener" <eddielee_at_[hidden]> wrote in message
> > Not true. std::wstring is no different than any other class (after all,
> > it's written in C++ - all the source code is in the header). If two
> modules
> > that were compiled with different settings for /Zc:wchar_t attempt to
> > exchange wstrings, there are two possibilities. !) If std::wstring is
> > coming from a DLL or static library, then there will likely be errors at
> > link time.
>
> No, there won't as long as the interface specifies just std::wstring. MS's
> name mangling only changes when wchar_t is part of a signature, but not if
> std::wstring is part of a signature.

Are you sure the signature of std::wstring itself isn't different though? I
actually haven't checked - it would have been under the VC6 mangling rules,
but if they're treating the std:: classes specially (with abbreviated names
in the mangling) then you're absolutely right - there would be no detection
at link time.

-cd


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk