Doug Turner wrote:

> I am pushing to freeze the core parts of XPCOM.  The reason is simple, 
> changes are busting users of xpcom clients.  There needs to be a 
> definitive list of the frozen API which embedders and xpcom developers 
> can reference.


Are there any plans to add support for component versioning to XPCOM in 
before this freeze?  Once we freeze XPCOM, can we start versioning the 
shared library as well?

Are there any plans for creating a separate lib for the "non-core" parts 
of XPCOM?  I vaguely recall another thread on this long ago but I can't 
seem to find it.

- cls



Reply via email to