Doug Turner wrote: > Christopher Blizzard wrote: > > >>Yeah, looks like we have some defacto freezing going on here. We are >>beholden to binary plugins already. ( Yucky again. ) >> > > The alternative is more... yucky. Suppose we do not offer any backward > compatibly. Suppose also that you download a plugin that was build against > 0.92. You install it in your new build running with our new xpcom frozen > APIs. You go to a page that uses the xpcom plugin. Guess what, it will not > display a message that says that something is wrong, it will do something > much worse: it will just crash. > > I don't have the intestinal fortitude to tell all the early adopters to > rebuild, retest, and reship newer versions of their plugins asap. I also > can't tell major embedders of mozilla that all the current plugin that use > XPCOM will crash their embedding client. Just really not a good idea IMO. > > doug turner > [EMAIL PROTECTED] >
I wasn't suggesting that you break compatibility. I was suggesting that you leave nsIServiceManager named as is and avoid playing games with casts. --Chris -- ------------ Christopher Blizzard http://people.redhat.com/blizzard/ Mozilla.org - we're on a mission from God. Still. ------------
