Mike, The rebuttal position: someone not long ago reported having to disable the OB debugger in order to "be able to use Pharo." FWIW, I was having some problems myself, and changed debuggers based on that report. My problems might have been due to a corrupted image, so changing debuggers might have been irrelevant to my ultimate climb out of the hole by building a new image.
Your point about not spreading ourselves too thin is well taken, but I also wonder whether we should expect to have high end tools and a set with more modest demands on the cpu. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Roberts Sent: Sunday, July 05, 2009 6:06 AM To: [email protected] Subject: Re: [Pharo-project] Call: identifying issues relevant for 1.0 I know it is quite a job, but I would like to see the core debugger fixed and maintained - or removed. #709 is a serious issue unless someone has recently fixed it. I have not used the OB one too much, so I guess it comes down to a discussion of what the official tool-set actually is for Pharo. I don't think we really have the bandwidth to maintain two toolsets, but we are currently keeping them around. thanks, Mike _______________________________________________ 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
