> I
> do think Spoon will put us in a better position to solve them.
> Specifically, it will help a lot to have completely unconstrained
> class
> names, ...

I don't understand this.  What do hard-references to classes in code
bind to then?  For example, two totally different Person classes are
loaded and one code says:

  myPerson := Person new

and other:

  someOtherKindOfPerson := Person new

Ah, is there a conflict-checking operation that dynamically renames one
of them?

Thanks..