by using the message "self halt" inside any method. When it reaches this message it will stop execution and pop up the debugger, from there on its just a matter of using the debugger to inspect the variables and move execution one step at a time, the true power of smalltalk. This way you can see exactly what code is executed and how it affects the variables. Of course you can do this with other IDEs too but where it gets real interesting is that the smalltalk debugger allows you to change the code on the fly thus perform tests on the code to see how it behaves.
On Wed, Jan 14, 2015 at 3:56 PM, nacho <0800na...@gmail.com> wrote: > Ben, > How do you actually use the halt method? > I don't follow you. > Seems like an interesting thing to explore. > thanks > Nacho > > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: > http://forum.world.st/Becoming-proficient-in-Pharo-tp4799284p4799495.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
