@Sean, ��In what way will it make halts more annoying?�� As far as I can tell, it eliminates FIVE mouse-clicks from #halt, and #haltOnce behaviour is unchanged. ��

Now ideally the debugger should not step into the halt at all when you <Step Over> - but this change��eliminates FIVE mouse-clicks from #halt, making #halt behave the same as #haltOnce. �� I can live with that. �� Lets do the simple thing first (the ticket has been open 11 months), and leave the potentially harder thing to make it right later on - unless of course this creates other problems.

On Mon, Jan 26, 2015 at 5:25 PM, Nicolai Hess <nicolaihess@web.de> wrote:

2015-01-25 0:22 GMT+01:00 Sean P. DeNigris <sean@clipperadams.com>:
Ben Coman wrote
> Anyone see a problem with removing
> that last condition?

Off the top of my head... Yes that doesn't seem like a good idea. You don't
want to find yourself inside Halt. You want to be in your code.

But isn't it already like�� that in case of #haltOnce ?

��
Although the
change makes this weird exceptional-sounding case better, it looks like a
hack that will make halts more annoying in general. The question is why you
end up deeply buried in the internals of Halt and how to prevent that in
this odd case.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Issue-12970-16-steps-to-get-through-halt-PROPOSED-FIX-tp4801405p4801457.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.