> it is
> unclear in which class the method should go (e.g., the class you're working
> or one of its superclasses?!)

Or one of its subclasses...

> And I really don't think we should do it.

Me neither.  Nor for the autoDeclineMembership thing.  In fact, not for any
kind of automatically-instantiated method.  (Maybe with the exception of the
setter/getter thing, but I always leave the preference turned off anyway.)

One of the most annoying things in VW was its insistence on
instantiating "prototype" methods in classes belonging to disjoint
hierarchies where I'd deliberately removed some of the basics (class,
at:, at:put:, doesNotUnderstand:, isNil, etc...) to do more
interesting things.  What's worse, it was the VM that did this
auto-instantiation for me, under my feet, without any recourse to
sanity whatsoever...

Ian