Patrick Bernard wrote: > Hello > >> "Normal" is that your instance will live until references to it have >> been removed. There could be other references elsewhere that you didn't >> mention. In case your object is implemented in Java, it's possible that >> you have to wait until the garbage collection kicks in. I don't know >> (I'm no Java expert) if this probably never happens in case the VM shuts >> down before the regular garbage collection has been executed. > > When the object is created, it is directly passed to the addEventListener > function and no reference to it is kept in my extension. > Besides, the extension is completely implemented in C++.
So it might be that the GlobalEventBroadcaster is not destroyed also. But to verify this it needed some investigation. >> The interface was set to "deprecated" because we wanted to fix a name >> clash. Unfortunately that never happened. So it's time to think about >> that and either revert that state of that interface or finally fix the >> problem. I have to investigate that before I can answer you question. > > I know that unpublished interfaces or service are not yet stable and can be > removed, but I don't know how this happens. Can this removal happen in a > minor update of OpenOffice.org ? When an unpublished interface/service is > replaced by another one, how long is it kept, so that code using it can be > modified ? Theoretically an unpublished interface can be changed at any time, in any release. So it depends on the individual case. As I wrote, I have to investigate the GlobalEventBroadcaster case before I can tell what will happen here. A short look tells me that this service declaration is "old style", so in practice nothing more than documentation. I assume that the name won't change, but the supported interfaces. I could imagine that the deprecated css.document.XEventBroadcaster interface might be replaced by css.document.XDocumentEventBroadcaster. I don't think that this change will be done in a minor version, perhaps 4.0 would be a good release for that change. OTOH it's still possible that we don't find the time to change our code for that and so it might remain for another few releases. Regards, Mathias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
