On Fri, 10 Jan 2003, Dan Kegel wrote: [...]
I don't know the particulars, but I do know that g++'s ABI only very recently stabilized.
^^^^^^^^^^^^^^^^^^^^^^^^ Isn't that a contradiction in terms?
[...]
(There was one little ABI tweak between 3.2 and 3.3, and there may be more later, but they probably won't break many apps.)
That too seems incompatible with something declared 'stable'.
Not that I have anything against C++, I like OO programming. But these g++ compatibility issues have been like a cold shower.
<rant class="my opinion only">
From the point of vue of an ISV, distributing a Wine binary is already
enough trouble with the C library changing their internal implementation (which of course they are absolutely free to do since it's *internal*) and FreeType breaking backwards compatibility in minor releases, but if ISVs also have to deal with g++ changing their ABI on a regular basis... Well, I guess ISVs could always compile these libraries with Visual C++ and ship them as Windows dlls and thus benefit from a stable and Wine compatible ABI... </rant>