Hi Stephan, > 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.
Perhaps we should have such a mechanism then. Going away from the "every released API must be stable" paradigmn by introducing the "published" keyword/feature was a great relief, and prevented some immature interfaces already (we have enough of them in the API created before). Now what you're saying is that efectively, we're in the same situation, again: Don't change any released API, as existing extensions might rely on it, and will disbehave (and probably crash, if they're C++) if used in conjunction with the new API. This makes, IMO, the "published" concept absurd. Said that, I strongly vote for having a versioning mechanism. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
