2015-11-09 13:37 GMT+01:00 Sean P. DeNigris <sean@clipperadams.com>:
Thierry Goubier wrote
Are you sure it would eliminate the gotcha? Can't you trigger it again with self classname: 1?
By "gotcha" I mean specifically doing something that seems normal that unknowningly breaks the system, added by the extra pain in this case that you might not find out until much later and not be able to connect the cause.
If someone sends #classname:, or even assigns to #classname, they deserve a broken system ;)
Thierry Goubier wrote
I like the elegance of AClass name.
Yes it's nice, but IMHO as a tremendous price. This is a constant pain point for newbies.
Come on; just an assert: aString isString in #name: would certainly stop the student doing any harm. We're talking of classes here, that is well predefined entities with a large API that one should not override... Now, about name in Object... Thierry
----- Cheers, Sean -- View this message in context: http://forum.world.st/Woe-unto-thee-who-assigns-to-class-side-name-tp4859734... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.