> > Yes but I do not work on >>>> - new first class instance variable >>>> - byecode loader >>>> - new package to speed up everything >>>> - scripting syntax >>>> >>> >>> Never mind, when I said "you", it was not specifically you, but anyone >>> else prefering to wait because of no free time. >>> >>>> so at the end I'm not sure what we lose but they are >>>> simple actions that other people can do too to distribute the load. >>>> So may be I will stop looking at squeak log. >>>> >>> >>> Sure, the danger is to become a follower of random activity driven by >>> others. >>> If time is sparse, you might prefer to keep control. >>> But some changes like file buffering really makes a difference. >> >> Yes but tracking changes you do not know is also taking time. >> I started but so far failed two times because you have to go slowly not to >> break too much the system. >> Tomorrow I will follow the advice of levente and check. >> The problem also is that the level of the tools is not really good. > > That shouldn't be hard: in a updated Trunk image, file out > MultiByteFileStream and StandardFileStream. Open a File Browser in your Pharo > image select one of the files, right click and select "code-file browser". > This will show you all the methods in the file and will diff it with the > current versions (if it exists). The annotation pane shows the timestamp and > information about the method (new, identical, modified, etc).
ok I will try like that. usually I check all the deltas in chronological order and skip what is not needed and wished. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
