The irony is that there is no such bug in Squeak. Class does not require such selector. But it "inherits" it in Pharo because of Trait implementation (via TClass).
Why Trait itself requires #name: is another question... IMO it does not. If I replace the two local send in Trait by direct i.var. access in Squeak, then the TraitsTests-Kernel all pass... Class has #setName:, though which is used in ClassBuilder, #obsolete and ImageSegment. So the same problem exists if you replace name: by setName: but it's a bit less likely. 2017-08-19 23:19 GMT+02:00 Sean P. DeNigris <s...@clipperadams.com>: > Stephane Ducasse-3 wrote > > any idea is welcome > > From > http://forum.world.st/Woe-unto-thee-who-assigns-to- > class-side-name-td4859734.html > : > Issue 16947: Class-side Inst Var "#name" Allowed, But Breaks System > > https://pharo.fogbugz.com/f/cases/16947/Class-side-Inst- > Var-name-Allowed-But-Breaks-System > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ > Lowering-the-pain-of-newbies-tp4961937p4962584.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
