Does this mean that gofer depends in yet-to-be-integrated closure fixes? That's fine, but it would probably stomp on my plan/hope to have gofer help me organize getting out of my current image and into an up-to-date one.
Maybe the refactoring code checker that Lukas mentioned is "hidden" by my current choice of toolset and will do the job. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Roberts Sent: Sunday, September 20, 2009 9:27 AM To: Pharo-project Subject: [Pharo-project] Closure fixes If you are interested in testing the closure fixes, I have scripted it. Run each section in turn. I have a few things for discussion, but first some feedback would be useful. Cheers, Mike "A. Load Gofer" ScriptLoader new installGofer. "B. Install packages" | gofer | gofer := Gofer new. gofer url: 'http://www.squeaksource.com/PharoTaskForces'; addAll: #( "Part 2" 'Kernel-MikeRoberts.405' "Part 3" 'Compiler-MikeRoberts.130' 'CompilerTests-MikeRoberts.21' 'KernelTests-MikeRoberts.150' "Part 4" 'Compiler-MikeRoberts.131' "Part 5" 'Kernel-MikeRoberts.406' "Part 6" 'Kernel-MikeRoberts.407' "Part 7" 'System-Changes-MikeRoberts.13' 'System-Download-MikeRoberts.11' 'System-Support-MikeRoberts.89' "Part 8" 'Tools-MikeRoberts.202' "Part 9 - setup recompile" 'System-Support-MikeRoberts.90' ). gofer load. "C. Recompile" Utilities initializeClosures. Utilities compileUsingClosures. "D. Run the tests please" TestRunner open _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
