Doug Turner wrote: > Furthermore nsISupports is complete frozen - if you want > to change it (which will never happen cause we claim to be binary > compatible with MSCOM), you would have to do a new interface and IID.
Binary compatible? I missed this one! Where is that claimed? How can that claim be made when XPCOM does not require (1) a call to CoInitialize, (2) entries in the windows registry and (3) component creation by CoCreateInstance. Sorry to sound stern, I just thought XPCOM's goals were to be comparable, but not necessarily compatible. -rick
