sort: vs sorted:

> Hi!
>
> MooseGroup has #sorted: and #sort:
>
> What about keeping just one?
>
> Especially since
> MooseGroup>>sort: aBlock
> self sorted: aBlock
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Hi Alex,
>
> This is there for compatibility reasons with older Pharo Collection implementations (there was a large debate a version or so ago). Now, we can rely on sorted: nicely, so we can remove sort:.
>
> Cheers,
> Doru
>
>
> On 15 Mar 2011, at 21:10, Alexandre Bergel wrote:
>
>> Hi!
>>
>> MooseGroup has #sorted: and #sort:
>>
>> What about keeping just one?
>>
>> Especially since
>> MooseGroup>>sort: aBlock
>> self sorted: aBlock
>>
>> Cheers,
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev