Benoit Thiell wrote:
I'm currently developping an application and use an unpublished API
because it saves me lots of work. What I was thinking as a provisory
solution is to add the possibility for a developper to suscribe to the
unpublished API and get a warning message when there will be some work
done on it. So the developer came immediatly publish a new version of
his application.
This might help in making sure that a working extensions version
corresponding to each OOo version is available, but it would not help in
making sure that each user of that extension has a version corresponding
to his OOo version, and that a broken combination of extension and OOo
versions would be detected at deploy or runtime.
-Stephan
Cedric Bosdonnat wrote:
Hi Stefan,
Stephan Bergmann a écrit :
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.
Something that could be possible is to add a warning in the code when
the UNO component/OOo extension writer uses an unpublished type, as for
deprecated types in most decents IDEs. I have no idea of how to do it
now, but this should be possible and would prevent a lot of these
errors. I'll think about this for the eclipse integration.
Cedric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
