Hannes Hirzel wrote > Which other kinds of problems do you see with this method? > Could you elaborate a bit please why you want to remove Object>>name?
Off the top of my head, in the worst case implementing #name on the class-side can be fatal. Less seriously one can get confusing result if e.g. you create a #name instVar and expect something to fail because you haven't created the getter yet, but instead it surprises you by using the unkown default implementation. At minimum, it creates confusion by using an overly generic name deep in the system. There should be as few reserved words like #class as possible, and only with very good reason, as it makes the system harder to understand. For more info, see: http://forum.world.st/name-tt3739677.html http://forum.world.st/name-selector-tt4760402.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Removing-name-from-Object-tp4847514p4847640.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
