* To Do:
* Need to remove nsIEnumerator interface. ( 99136 )
Read bug 99136
Rick,
nsIComponentManager has got to change a bit. See bug 98553.
Do these changes break xpcom plugin's. Don't know. CC-ing beard, av.
Mike Shaver wrote:
> Rick Potts wrote:
>
>> I believe that nsIEnumerator is our first frozen, depricated interface
>> :-)
>>
>> nsIEnumerator is considered frozen because nsIComponentManager exposes
>> it. I believe that nsIComponentManager has been considered frozen
>> (for the past year+) because of its usage by plugins.
>
>
>
> I'm not buying it. XPCOM isn't frozen yet, none of those interfaces
> went through API review prior to being "frozen", and there's all sorts
> of cruft in nsIComponentManager that needs to be taken out. That's
> _why_ we're going through this freezing exercise.
>
> I'll buy the need to support the 4.x NPAPI for plugins, but it would be
> the height of folly for us to sign up to long-term support for the
> "new-style" XPCOM plugin interfaces; they're a disaster.
>
> (And nobody writing a plugin is going to be using enumerateContractIDs,
> I assure you. Changing it to return nsISimpleEnumerator -- rebranded
> nsIEnumerator, I hope -- won't hurt a thing.)
>
> Mike
>
