Re: reminder: please add "API CHANGE" to commit message if you change the API incompatibly
On 30/07/2015 20:04, Michael Stahl wrote: * Python PyUNO pyuno/ I think we discussed this the last time I changed it - the external C++ interface in pyuno/inc/pyuno/pyuno.hxx shouldn't be considered "really public", and its comment explicitly states "This interface is somewhat private and my change in future." I can mark any future changes to it that way if you'd like, but anything outside core LibreOffice still shouldn't depend on it for binary compatibility. Given that it seems to exist solely to allow PyUNO itself to be compiled as a (bundled) library, it's hard in any case to imagine how or why anyone would use it for anything else. Regards Matthew Francis ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: reminder: please add "API CHANGE" to commit message if you change the API incompatibly
Hi, On Thu, Jul 30, 2015 at 02:04:03PM +0200, Michael Stahl wrote: > as a reminder our public API consists of the following: > > * UNO API > udkapi/ > offapi/ > > * C++ URE > include/com > include/cppu > include/cppuhelper > include/osl > include/rtl > include/sal > include/salhelper > include/systools > include/typelib > include/uno > > * Java URE > javaunohelper/ > jurt/ > ridljar/ > > * Java Bean > bean/ > > * Python PyUNO > pyuno/ > > * codemaker is effectively sort of part of the ABI, in case the > generated code would change in an incompatible manner > > * Configuration > officecfg/ > > there are probably more obscure bits that i forget... do ActiveX or OLE > automation bridge define any LO-specific interfaces? We should probably add: * Scripting framework scripting/java * XMerge filter framework xmerge D. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: reminder: please add "API CHANGE" to commit message if you change the API incompatibly
On 30.07.2015 14:04, Michael Stahl wrote: > as a reminder our public API consists of the following: ... and i forgot this one, we haven't had any incompatible changes in it yet: * CLR/.NET UNO cli_uno/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
reminder: please add "API CHANGE" to commit message if you change the API incompatibly
as i recently noticed while finally writing the API change section for the 4.4 release notes (and it was about time...), almost none of the commits that do change the API in some (theoretically or practically) incompatible way between 4.3 and 4.4 had the required "API CHANGE" notice in the commit message, which made writing the release notes more difficult. please if you change something incompatibly in the API put the required "API CHANGE" marker in the commit message. as a reminder our public API consists of the following: * UNO API udkapi/ offapi/ * C++ URE include/com include/cppu include/cppuhelper include/osl include/rtl include/sal include/salhelper include/systools include/typelib include/uno * Java URE javaunohelper/ jurt/ ridljar/ * Java Bean bean/ * Python PyUNO pyuno/ * codemaker is effectively sort of part of the ABI, in case the generated code would change in an incompatible manner * Configuration officecfg/ there are probably more obscure bits that i forget... do ActiveX or OLE automation bridge define any LO-specific interfaces? PS: Matus gets a honourable mention since while he did forget to add it in the commit message he at least added the change to the release notes himself ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
