+1 On Jan 22, 2013, at 6:45 PM, "Gary Chambers" <gazzaguru2@btinternet.com> wrote:
+1 to removal...
Regards, Gary
----- Original Message ----- From: "Sean P. DeNigris" <sean@clipperadams.com> To: <pharo-project@lists.gforge.inria.fr> Sent: Tuesday, January 22, 2013 5:02 PM Subject: Re: [Pharo-project] Object>>#name
Sven Van Caekenberghe-2 wrote
Many people have hit the fact that Object implements #name, which then seems to conflict with some other class where one would really like to use name as an instance variable and thus accessor.
Yes, I've been bitten by this a few times. When developing through the debugger, it's confusing when the thing fails silently instead of prompting to create the method.
Sven Van Caekenberghe-2 wrote
Turns out that it seems that Object>>#name is actually not used (anymore).
There are lots of senders... I guess they're sending Class>>#name or another message. I say ditch it, but wait until 3.0...
-- View this message in context: http://forum.world.st/Object-name-tp4664573p4664583.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.