With the introduction of RPackage, Pharo 3 introduced
ClassDescription>>packages to return the rpackage of a class
and its extending rpackages. This conflicts with
GRPackage>>packages. There was no test for this, and
Pharo contained a few more classes that implemented
>>packages. In a slice for Pharo issue 12324 (not integrated yet)
I now added a test that makes sure that no class implements
the method, so it is no longer a silent failure.
What would be impacted by changing #packages to #grPackages?
Stephan
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Locked
