I strongly feel that there *must* be a short (but non-zero) amount of time between *changing* the interface and *freezing* the interface. I appreciate that you are making these changes. But, I think it is wrong to simultaneously whack the tree and claim that you got it right and it can't change. There needs to be a short period of time after the interface change during which the interface is marked as "about to be frozen". This gives people a chance to see if the change had some unanticipated effect and some time to bring that to public attention before the FROZEN stamp is applied.
John. Doug Turner wrote: > > The nsIObserver and nsIObserverService are now frozen: > > nsIObserverService > http://lxr.mozilla.org/seamonkey/source/xpcom/ds/nsIObserverService.idl > > nsIObserver > http://lxr.mozilla.org/seamonkey/source/xpcom/ds/nsIObserver.idl > > Please note, that you can track the progress of XPCOM API changes on > this bug: > > http://bugzilla.mozilla.org/show_bug.cgi?id=98278 > > Please note that this interface is frozen. It will not change and you > can depend on it. The only interfaces that are frozen are marked: > > http://lxr.mozilla.org/seamonkey/search?string=us+frozen > > If your component or plugin is using interfaces outside of this set, > please note that they are most likely unfrozen and have the possibility > to change. > > doug turner > [EMAIL PROTECTED]
