On Jun 17, 2010, at 12:27 PM, Lukas Renggli wrote:
I've tried to post a message on the bug-tracker, but it seems to have some troubles at the moment. So I post it here:
- If included with Pharo I suggest to rename all the methods, otherwise we will run into big troubles with Seaside and other projects that depend on Grease.
why? you cannot have a Pharo package for grease where these methods are not present?
- If included with Pharo I suggest to also include the tests from Grease-Tests.
- The #trim protocol is just a subset of various related string manipulation methods. It is kind of a pity to take that apart. Why not keep Grease-Core as an externally loadable package? It has no other dependencies.
why not
Lukas
On 17 June 2010 11:57, Serge Stinckwich <serge.stinckwich@gmail.com> wrote:
Hi Adrien,
i think it's much better if you include some tests also.
Regards,
2010/6/17 Adrien BARREAU <abarreau.dev@live.fr>:
Hello all,
The trim* messages defined in Grease are really useful. I suggest to integrate them in the String class.
Take a look: http://code.google.com/p/pharo/issues/detail?id=2560
Adrien.
________________________________ Vous voulez protéger votre vie privée ? La solution avec Internet Explorer 8 _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
_______________________________________________ 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