> > The system we are working on will be using XPCOM and we were thinking of
> > running the autoregister at the startup of the program (I guess we were
> > really counting on running it actually...)
> >
> > So I looked into the default implementation of nsIModule (the interface
> > which defines the method canUnload( ).) Here are the tragic results:
>
> This is a problem the first time you autoreg when everything gets loaded,
> but on subsequent registrations AutoReg only loads new modules and ones
> which have "changed" as determined by timestamp and file size.
>
Right, so it is not as big of a deal as it might otherwise be, but it is
still a pretty big hole (at least if XPCOM wants to grow out of it's Mozilla
roots at some point...)
Ken
