Not a duplicate, at least not of 17798.
Sent: Thursday, March 10, 2016 at 4:35 PM From: monty <monty2@programmer.net> To: pharo-dev@lists.pharo.org Subject: Re: [Pharo-dev] feedback from yet another student presentation
Sent: Thursday, March 10, 2016 at 4:14 PM From: "Alexandre Bergel" <alexandre.bergel@me.com> To: "Pharo Development List" <pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] feedback from yet another student presentation
- it was reallllly hard to register a project on smalltalkhub just after we created an account. This already happened to me during the open-devs. So this is a really big show stopper for the mooc. Because people will gave up just after the first lecture :(
The situation will be much easier I hope once git is well supportedâ¦
- we should really rename Class>>name: into setClassName: students were manipulating object with name such as state of state machine and one wrote
State name: 'A' and just rename the class and broke the system.
I have just created an issue: https://pharo.fogbugz.com/f/cases/17798/Rename-Class-name-into-setClassName
Marked as a duplicate of: https://pharo.fogbugz.com/f/cases/7241/Object-name-should-best-be-removed
This has been an issue for years.
Leave it as-is and anyone defining a class-side name: constructor risks breaking any tooling that still relies on name: renaming a class. Use named: (much more common in the image) instead and nothing will break, but now anyone that mistypes the selector as name: (no "d") accidentally renames the class, and to a string instead of a symbol.
Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.