Hi Mathias, > I'm still not convinced that every type should be allowed to change. I > think that stable types have their value. But we have to find out.
Well, between 1.0 and 10.0, I think nearly every API should be allowed to change. Else 10.0 will consists of zillions of XFoo10 interfaces, and zombie versions with numbers below 10. > What I especially wouldn't like is the following situation: I have > written an extension that runs fine in, say, OOo 2.x. I also didn't use > any types that have been changed incompatibly in OOo3.0 but as this > release is announced to be API-incompatible my extension is not usable > reliably. How can we avoid that? How can an extension find out whether > it is still compatible to the current OOo version? By the author, or somebody else from the community, trying it out. > I hate how it is done in TBird and FFox where extensions are disabled > just because the version number changed but still run fine after some > manual fiddling in the version information of the extension (something > end users shouldn't need to do). I think this works pretty well. Of course there are false negatives often enough, but usually they're fixed fast. And the cases where the negatives are right (usually between major upgrades) show that some restrictions in fact *are* necessary. As Thorsten said, even syntactic compatibility doesn't mean you're free from testing your extension with the next release. Ideally before your users find out it doesn't work anymore. All in all, I could pretty well live with an approach as in TB/FF. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
