I've been running 3.5 for awhile now, and am just starting to play with 3.6. I've noticed a difference in the debugger.
In 3.5, I could have "browseWithPrettyPrint" turned on, and everything was just nifty.
But in 3.6, when I have "browseWithPrettyPrint" turned on, the debugger tries to highlight the code as if the pretty printer was *not* turned on. This makes the debugger completely worthless unless I turn pretty printing off. And, since the debugger is an absolute necessity, the debugger trumps the pretty-printer, thus making the pretty printer worthless.
What happened? Anybody know?
I sure miss the pretty printer, and I'm not inclined to upgrade without it.
Nevin
Nevin Pratt wrote:
I've been running 3.5 for awhile now, and am just starting to play with 3.6. I've noticed a difference in the debugger.
In 3.5, I could have "browseWithPrettyPrint" turned on, and everything was just nifty.
But in 3.6, when I have "browseWithPrettyPrint" turned on, the debugger tries to highlight the code as if the pretty printer was *not* turned on. This makes the debugger completely worthless unless I turn pretty printing off. And, since the debugger is an absolute necessity, the debugger trumps the pretty-printer, thus making the pretty printer worthless.
Some good news for you... this is fixed in 3.7beta. But it is a problem in 3.6.
What happened? Anybody know?
Most likely part of the general mayhem following the block context enhancements in 3.6. ;-) But the remaining problems seem to be solved in 3.7 now as far as I can tell.
- Doug
Doug Way wrote:
Nevin Pratt wrote:
I've been running 3.5 for awhile now, and am just starting to play with 3.6. I've noticed a difference in the debugger.
In 3.5, I could have "browseWithPrettyPrint" turned on, and everything was just nifty.
But in 3.6, when I have "browseWithPrettyPrint" turned on, the debugger tries to highlight the code as if the pretty printer was *not* turned on. This makes the debugger completely worthless unless I turn pretty printing off. And, since the debugger is an absolute necessity, the debugger trumps the pretty-printer, thus making the pretty printer worthless.
Some good news for you... this is fixed in 3.7beta. But it is a problem in 3.6.
OK.
How do I advance my system to 3.7? It used to ask me if I wanted to advance to the next rev.
As far as my 3.6 goes, I got it from squeakland.org.
I am wanting to run this on a Mac (Panther). Does the 3.6 VM still work with 3.7? If not, where do I get the new one?
Sorry for all the piddly questions...
Nevin
squeak-dev@lists.squeakfoundation.org