Hi: On 16 Jan 2012, at 14:31, Camillo Bruni wrote:
> I guess having the sources completely in the image is the straight-forward > solution to this :/ Well, we could also cache just the resulting source string. Not sure what that means in terms of memory, but going to the file every time a method is asked for its code seems to be very naive. How does Ring do it? > or using a native tool to grep the source files and then use the results to > map back to the methods Ehm, that sounds very brittle, except if you got a nice file representation of your code of course ;) Levente pointed out to me that he introduced a smarter approach to caching in Squeak, with similar performance improvements, and he was thinking about improving that to a process-local variable. Perhaps also an option. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
