Laurent Godard wrote:
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
it's primary a reminder that API designer should be careful with
"unpublished" API's and that developer should take into account that an
unpublished API can be change and that their solution may not work with
the next release. The main goal should be to publish new API's when they
are released with an official release or at least one release later. We
know that it isn't ideally because we have found specification errors in
API's later when they already have been published. Ideally we would have
a real versioning concept for UNOIDL types but that is not available for
several reasons.
Currently we have ~700 unpublished types and that are to many. We will
review this types, adapt them where possible to make use of new UNO
features and will publish API's which are not primary designed for
internal usage.
Juergen
if valuable (still do not know), dicussions may occur at here or better
at [EMAIL PROTECTED] mailing list
thanks again
Laurent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
