On Tue, Dec 11, 2012 at 8:58 AM, adrians <nman...@gmail.com> wrote: > > > Of course not all of what needs to be done in Pharo should be of at same > priority. It makes sense to first fix the tools one uses for fixing > everything else, so that one can speed up one's own work and at the same > time open up the possibility for others (less skilled) to help out. > > In any case I'm sorry if it seems that I'm demanding you or anyone else > should make this a higher priority. The thinking was that maybe there is > someone (Stephane D?) who, to some degree, can prioritize certain things > over others and if so, wouldn't it make sense to fix the most basic tool > that is used to help fix everything else? > > Who knows though, maybe the debugger is not often used by the experts. >
On the contrary. Many experts program in the debugger (one defines a method when one gets a doesNotUnderstand:). Many experts use the debugger to explore code (running code is a powerful aid to understanding). Some experts use the simulation machinery that underlies the debugger to do things like partial evaluation for type analysis etc. > -- Adrian > > > > -- > View this message in context: > http://forum.world.st/Helping-the-noobs-help-out-i-e-fixing-the-debugger-tp4658666p4658877.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- best, Eliot
