Yes we know but first we should just make sure that the system is still
working without this $#%^^&*^(&)*%^& method.
Le 2/9/15 10:29, Esteban Lorenzano a écrit :
but if we deprecate, that means we need to remove it from the system.
deprecated is for external users, not for Pharo it self.
Esteban
ps: We *can not* remove #name from the system just like that. It is
too widely use, we need to give users time to adapt. Doing otherwise
is not professional and expect a lot of people yelling (and with
reason, in this case).
On 02 Sep 2015, at 10:21, Guillermo Polito <[email protected]
<mailto:[email protected]>> wrote:
The problem is if (like in the past) name is extensively used by some
library we depend upon (like... let's say morphic), a deprecation
that raises an exception may turn the system unusable. It's not that
it is not doable, but we should do it gently and with love.
El mié., 2 de sept. de 2015 a la(s) 9:30 a. m., Esteban Lorenzano
<[email protected] <mailto:[email protected]>> escribió:
On 02 Sep 2015, at 09:25, Peter Uhnák <[email protected]
<mailto:[email protected]>> wrote:
On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <[email protected]
<mailto:[email protected]>> wrote:
How can we find out, which external projects depend on this?
Is #name in any way special? Why not just deprecate it like any
other method change or removal? (And then remove it in Pharo 6)
+1
that’s the way to do it :)
Peter
