we need to revert.
this is a huge mess in a very inappropriate moment :)
Esteban
> On 14 Nov 2016, at 13:56, Tudor Girba <tudor@tudorgirba.com> wrote:
>
> Hi,
>
> Indeed, I forgot that #selector is doing something else. This is a bit of a mess. Either we revert it today, or we leave it. Otherwise, more projects will adopt the new API only to break again afterwards.
>
> Doru
>
>> On Nov 14, 2016, at 1:50 PM, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
>>
>> On 14/11/2016 13:44, Tudor Girba wrote:
>>> Hi,
>>>
>>> Please do not revert the API. Just comment out the deprecation. The code in Moose was already updated to the new API and I presume other projects might be in the same situation.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>> www.feenk.com
>>>
>>> "Be rather willing to give than demanding to get."
>>>
>>>
>>>
>>
>> Changing the API without a deprecation phase is bad. This kind of
>> breaking change without warning is something companies can fear. This is
>> even more important when there is such a dangerous change. #selector is
>> still here but do something different��� This is bad to just change it in
>> one go.
>>
>> Maybe some projects updated but most companies do not follow the
>> development version of Pharo.
>>
>> --
>> Cyril Ferlicot
>>
>> http://www.synectique.eu
>>
>> 2 rue Jacques Pr��vert 01,
>> 59650 Villeneuve d'ascq France
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "It's not how it is, it is how we see it."
>
>