Le 20/2/15 15:59, Sean P. DeNigris a écrit :
As you know, I love cleaning ;)
But...
stepharo wrote
https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/StringCleaning.md
What enlightenment am I supposed to gain from "candidates for removal...
asLegalSelector", and later "Done: candidates for removal...
asLegalSelector". I still understand nothing of the rationale.
Yes we are poor are documenting such decision. But if to remove a bad
method it takes 5 times more energy than
removing it then we will never make progress.
This code is bogus and shitty.
And useful ;) (as evidenced by this thread). Okay, it's limited, but what's
better - having users roll their own every time?
Probably and I'm not provocating.
For now, I'll package it with my code, but I think we should add it back,
maybe with a method comment to clarify that it creates a unary selector
only...
Bring back #asLegalSelector
https://pharo.fogbugz.com/default.asp?14969
Fix in inbox: SLICE-Issue-14969-Bring-back-asLegalSelector-SeanDeNigris.1
I think that this is better that you package it with your app. I do not
see the point to have
this method fromGarbageToUnarySelector in String.
Stef
