I suggest that we just remove the two methods (Collection>>#sorted and Colection>>#sorted:) from Grease. It doesn't look like the system itself is calling them on Collection, and most subclasses override them anyway.
Lukas On 9 September 2010 11:10, Philippe Marschall <kus...@gmx.net> wrote: > Hi > > It seems like we unintentionally introduced an override for Collection >>> #sorted in Grease. That puts in a hard place because we can't simply > remove it from Grease. Because if you do that everybody who updates > looses the method and potentially breaks his image. Yeah, I see that the > real fix you be for Monticello to restore the old method but that hasn't > happened in years. > > Monticello / the compiler already warns about a lot of less important > things. Now I know adding an additional preference for that is ugly and > I'd welcome and better/nicer solution. > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
