Stef wrote:
>Do you think that if an external library redefines the semantics of #class, it will be a Pharo bug?

I don�t know. I know I have 35 implementers of #packages in my Moose image, and 191 senders.

And I know that in Magritte 3 we changed from using #description to #magritteDescription to avoid
polluting the namespace with a word that is commonly used for other things. At the same time
I don�t exactly enjoy adding prefixes everywhere. DeprecationFinder tells me there are 60 projects
on smalltalkhub using #packages. And I know I have to be careful about where I use #name.

And when taking a look at the problem, I immediately run into lots of methods flagged #todo, a.o.
(CompiledMethod>packageFromOrganizer:) that seems to suggest a different solution.

I can imagine a more effective way of convincing Grease maintainers that they should switch API :)

Stephan