I vote for setClassName: Brad Selfridge
> On Aug 20, 2017, at 5:30 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > Thanks for all the information. In Pharo 70 Object does not understand > name so it will already be a step in the right direction. > > I think that we should do two things. > - Address simply this problem for example using setName: or > setClassName: instead of name: > - start to prototype for a future a solution where the reflective > calls are clearly identified. > > Stef > >> On Sun, Aug 20, 2017 at 11:19 AM, Luke Gorrie <l...@snabb.co> wrote: >> On 17 August 2017 at 21:52, Stephane Ducasse <stepharo.s...@gmail.com> >> wrote: >>> >>> We should not accept such kind of behavior. >>> name: should not change the name of the class. >> >> >> I had exactly such a problem a couple of weeks ago :). >> >> I write MyClass on: foo; name: x; yourself'but I forgot the ^ return in >> MyClass class>>on: and so called name: on the class instead of the instance. >> Hilarity ensued :). >> >> >
