Uninstalling a package

I've seen this before and now I see it still in V5.  I'll uninstall a
package, during which I get a message saying that aClass has 1 instance(s),
do I still want to uninstall.  Whether I press ok or cancel, the uninstall
continues.  I'm not sure if the instance remains in the image.  The prompter
seems a bit misleading as to one's choices and the outcome.

"Louis Sumberg" <[hidden email]> wrote in message
news:[hidden email]...
> I've seen this before and now I see it still in V5.  I'll uninstall a
> package, during which I get a message saying that aClass has 1
instance(s),
> do I still want to uninstall.  Whether I press ok or cancel, the uninstall
> continues.  I'm not sure if the instance remains in the image.  The
prompter
> seems a bit misleading as to one's choices and the outcome.

In fact the message says:

    <class name> has <N> instances.

    Would you like to remove the *class* anyway?

i.e. it is prompting as to whether you wish to uninstall the particular
class, not the rest of the package. If you press No, the class remains (not
the package). If you press Yes, the class is forcibly removed. FWIW I always
press Yes in response to the prompt on the rare occassions that I see it,
but usually I go to another window and investigate the source of references
to the remaining instances (e.g. using ReferenceFinder).

Note that it is not possible to tell up front whether the instances of
classes in the package that exist at the time the uninstall is initiated
will still exist when the class itself comes to be uninstalled, since they
may only be referenced from globals in the package, or may be destroyed by
uninstall scripts or class uninitialize messages.

Regards

Blair

Blair,

> ... If you press No, the class remains (not the package).

Not for me, that's why I meant it was misleading.  If I press No, the class
is removed anyway.

I suspect it's continuing from a resumable error (somewhere within the
bowels of PackageBrowserShell>>uninstall:), but I wouldn't bet money on my
suspicions

Thanks for the other info in your response and the headsup on
ReferenceFinder.

-- Louis

"Louis Sumberg" <[hidden email]> wrote in message
news:[hidden email]...
> Blair,
>
> > ... If you press No, the class remains (not the package).
>
> Not for me, that's why I meant it was misleading.  If I press No, the
class
> is removed anyway.

It is possible that where a hierarchy of classes is packaged that one might
get the prompt for a subclass, but that subsequently when the superclass is
removed (which will also remove subclasses if there are no instances) that
it is successfully removed. An example is where the superclass provides
access to singleton instances of its subclasses and has an uninitialize
method that releases the singletons.

Regards

Blair