> Sure, that's why we version code. So I have to hunt around prior versions in the SCR just to discover who *really* wrote some method and when? Or, when debugging something and suspecting a method indicating recently "changed", I dig around the SCR, only to discover, "oh, actually Dan Ingalls' method really didn't change since 1999 afterall, it was just the assignment operator in 2010." Invalid accounting info all over the image. Sheesh, what a shame..
>> Just a friendly reminder that the FixUnderscores package is available >> to do this with preservation.. > > It's broken, it only works 90%. I've been using it for years with no problem. What do you mean "broken?" _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
