|
About what Ben said: 'changing it for real worth it the day of the "feature freeze" of Pharo 3.0'
I tried changing it for real, and it breaks things up to the internals of monticello! So if you want to do that, it will have very far-reaching consequences. I think it is a bad idea (for now). If you want to fix this in depth it will take a looooot of time. Look at the tests that failed on the first slice I submitted to get an idea ...
And in case you want to change it 'for real', this does not preclude the fix that I propose now. So integrate it :-) It will actually help people get used to the new subclass creation message I think.
|
|
|
Priority: 4 – Would be nice
|
|
Status: Resolved (Monkey is checking)
|
|
Assigned to: jfabry
|
|
Milestone: Pharo3.0
|
Go to Case
|
|