[Pharo-dev] Again on #definesClass: and #includesClass:

In environments we have two methods: #definesClass: and #includesClass:. They make sense for package environments, as one of them may include a class as it defines extension methods for it, but it’s not defining the class itself. Now #includesClass: is redefined in all environments, but #definesClass: is not redefined anywhere except for package environment. So for example ClassEnvironment says that it defines every class that it’s asked about. Should we redefine that method in each environment? I would say yes, but I’m not familiar with RB…Stuff philosophy. What do you think? Cheers. Uko