Hi all,
there are two issues with unpublished UNO API I want you (as both an API
author and consumer) to be aware of:
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.
And then, chances are that you will get complaints if you change the
unpublished API later on and those components/extensions stop to work.
That is, even if it would be technically sound to change an unpublished
API, there might be cases where there are sociological reasons that
effectively hinder you from doing so.
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.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
