On Fri, Oct 27, 2006 at 10:21:45PM +0200, Steinar Bang wrote:
> >>>>> Malcolm Rowe <firstname.lastname@example.org>:
> > I think some people are also concerned about maintaining compatibility
> > across g++/win32 and MSVC/win32. Then, the STL (etc) is more of a concern.
> What kind of compatibility are you referring to? Source code
> compatiblity? Or binary compatiblity?
> If you're talking binary compatiblity between g++/Win32 and MSVC++,
> you don't have it, and I don't think you ever will. But I don't see
> why that would matter?
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.
It matters because we wouldn't want people to need to worry about
whether the same compiler was used to compile the Subversion libraries
as was used to compile the client (Tortoise, etc). This may become more
of an issue on win32 in the future, as people were interested in making
Subversion compile using e.g. mingw.
Received on Sat Oct 28 14:07:49 2006
- application/pgp-signature attachment: stored