Hi Stefan
there are two issues with unpublished UNO API I want you (as both an API
author and consumer) to be aware of:
thanks for this reminder :-)
First, if you release some unpublished API that is badly needed by UNO
component/OOo extension writers to get their job done, chances are that
those writers will use your API in their components/extensions anyway.
I agree
Second, we neither have nor plan to have in place a mechanism to detect
that some UNO component/OOo extension uses an old revision of some
unpublished API. That is, there will not be any warning if you deploy
such a component/extension into an environment where it will not work,
and at runtime using that component/extension can have unexpected effects.
anything that can be done there by exploring the source code and checks
against the deprecated/unpublished status ?
this would be a tool for Extensions designer
if valuable (still do not know), dicussions may occur at here or better
at [EMAIL PROTECTED] mailing list
thanks again
Laurent
--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org
Indesko >> http://www.indesko.com
Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org
Livre "Programmation OpenOffice.org", Eyrolles 2004
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
