Re: refcount checking in add_interface

[Maciej Stachowiak <mjs eazel com>]

Nat Friedman <nat@helixcode.com> writes:

> Maciej Stachowiak <mjs@eazel.com> writes:
> 
> > 
> > The only way this invariant differs from "you may not add or remove an
> > interface after exposing an object" is that it allows the component to
> > add or remove an interface that has not been QI'd for yet. Is that a
> > useful difference? I can't imagine why an object would want to do this
> > rather than assembling all its interfaces ahead of time.
> 
> I don't know, but apparently it makes a difference because that check
> keeps getting removed.

If Elliot thought that Nautilus wants to do something the check
wouldn't have allowed, he was wrong.

> Dunno how to implement this.  Dubious that it can be done this way.

Me too, alas.

 - Maciej