<http://www.openoffice.org/issues/show_bug.cgi?id=82715#desc15>:
------- Additional comments from rene Thu Nov 8 09:21:22 +0000 2007 -------
FWIW, Sun seems to plan to get rid of it (for 3.0), too:
http://wiki.services.openoffice.org/wiki/OOo30_release_engineering_planned_changes
------- Additional comments from sb Thu Nov 8 09:42:11 +0000 2007 -------
@rene: ...but at least for the usage of STLport within the C++ UNO ABI we
cannot drop it, unless we drop compatibility (which we do not really plan for).
------- Additional comments from [EMAIL PROTECTED] Thu Nov 8 09:49:13 +0000
2007 -------
sb:
How should I read that page then?
The OpenOffice 3.0 code line will be the first chance in many years to do a
number of changes which will break the strict binary compatibility and
patching requirements on the current SRC680 code line.
"will break [...] binary compatibility requirements"
The following is a short list of changes which are planned before the first
release of OOo on the new codeline.
[...]
* get rid of STLport, use system STL where applicable
What we're discussing here ;-)
To not stretch hijacking cmc's issue too far, lets move the discussion here:
The binary compatibility release engineering is talking about on that
Wiki page is between OOo-internal libraries (so that new OOo minor and
micro versions can potentially be distributed as patches that include as
few files as possible). This is not related to the binary compatibility
guarantee for UNO's external ABI.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
