Thorsten Behrens wrote: > Hi *, > > on the last ESC meeting, we had a little brainstorming about if and > how to deprecate OOo API. The 'if' was unanimously agreed upon, > for the 'how' we came up with the following thoughts: > > API deprecation > ===============
There's one point in the wiki I don't agree with: > limit impact considerations to non-ABI-dependent UNO bindings (i.e. the > assumption is that c++ components break randomly anyway for every other > release, so they shouldn't block API changes) This is not true; in fact on Windows C++ extensions are very stable and at least without a base line change that should be true for other platforms as well (some discipline assumed). My take on that would be: if we allow for incompatible API changes in e.g. a major release, there's no reason not to allow incomatible changes in the C++ libs also. Maybe that's what you wanted to express. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "nospamfor...@gmx.de". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
