Doug Turner wrote: > 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'd have thought that the component manager would barf trying to load the plugin because of undefined symbols, and then return an error code. Do you really see it crashing when you use older plugins without your fix? Mike
