2010/1/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
ok I understand. I will keep your energy for the important one.
http://code.google.com/p/pharo/issues/detail?id=1856
but since I'm nearly the only that have a look at fixes in squeak may be I will simply just stop to look at them because the community does not seem to interested in getting them or producing them for pharo.
Sure some people are interested as much as you are. But waiting for someone to do the job for you, or wasting your own time is rarely a dilemna except for the happy few owners of "own time" ;) It's important to keep up with what's going on in other branches : kind of technology forecasting :) Just lurking the daily commit logs, and registering interesting stuff as pharo issue is already valuable. Nicolas
Stef
On Jan 20, 2010, at 8:27 AM, Nicolas Cellier wrote:
Don't know if I'll have time, but changes are fairly easy to grab (independent of each other).
Ok
Nicolas
2010/1/19 Stéphane Ducasse <stephane.ducasse@inria.fr>:
Hi nicolas
I saw that you commit some speed up for lineending to the squeaktrunk and I would love to have them since in moose we are computing a lot LOC :) By any chance could we get the same in pharo? Else I will harvest them.
Stef _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project