On 10/30/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> On 10/28/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> > I meant binary compatibility. My understanding from speaking to Dan
> > earlier was that g++/win32 follows the vendor-defined ABI (that is,
> > MSVC on Win32) for C++, so we should be okay as long as we don't expose
> > anything to do with an STL implementation.
>
> Messages on the GCC list earlier this year from Mark Mitchell hints
> that there is no ABI compatibility between MSVC and g++ and won't be
> any time soon:
This is correct.
We can't implement the MSVC C++ ABI even if we wanted to, due to
patents. However, on all other platforms, the C++ ABI is cross-vendor
and compatible across compilers. If I gave the impressiont that we
follow the MSVC abi on win32, this was incorrect.
Anyway, this discussion is a bit, well odd.
I'd rather see it go like this:
Tell me what situation you believe users are going to run into C++
problems with, and i'll tell you how to solve it.
Because seriously, on win32, people use MSVC compiled binaries, and
on unix, most people use packages or compile from source code.
So uh, which users are we worried about trying to mix incompatible libraries?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 30 16:05:13 2006