On Dec 12, 2012, at 11:28 PM, adrians wrote: > > Well, it just seems that I'm whining here instead of contributing, but if > the debugger is indeed a very (if not the most) useful tool which is used in > pretty much every bit of fix-up work, fixing it if it is broken would have > to come before all else, no? Otherwise, any work that needs to be done until > it is looked at is just compounded. > > Maybe it would make sense to correct (in the current code) to a small degree > just one of the things that is currently broken. No frills, but just getting > a more accurate indication of where the PC is - at least have it on the > correct line of code if it can't be pinpointed more accurately without too > much hassle. I'm curious what derails the location highlighting as half of > the time it is close, if not correct. Is it blocks that give it a hard time? > It wouldn't be too bad if other things were going to take a while if you > could at least keep track of where you were. > > If the idea is to wait until a whole big refactoring can be done on this, I > fear a fully debugger might be another year away.
Your analysis is right. No this is not the idea. We never waited for big bang. But frankly I invite to come in our team to see us fully busy. Because we are doing far more than Pharo. Stef > > -- Adrian > > > > -- > View this message in context: > http://forum.world.st/Helping-the-noobs-help-out-i-e-fixing-the-debugger-tp4658666p4659105.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >
