2005/5/12, Mathias Bauer <[EMAIL PROTECTED]>: > > Anyway, in all cases (no documentation, derived or versioned services) > you need to use queryInterface to get the desired interface and you need > to check the return value,
Technically yes, but in practice there's no point to doing the check, because there's nothing my application can do to recover if it fails. Whether my application exits with a NullPointerException or with an error message "Sorry, but the OO developers have made an incompatible change, so this program will no longer work." is solely a matter of aesthetics. For the user the only thing that matters is that the program has stopped working after updating to a new OO version. But is this likely to happen? Will office documents in OO 2.1, 2.2,... 3.0, 3.1 no longer support XScriptProviderSupplier? I doubt it. If there's no way to document this at the moment, that's a shortcoming of the IDL that may be worth fixing. Rather than having an interface "mandatory" or "optional" there could be a versioned property such as "mandatory since UNO version x.y". Matthias Benkmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
