Ben,

I don't think you can compare #halt with Breakpoints. Breakpoints have two main advantages over halts:


So when you work on code to actually ship into users' hands, there are quite some good arguments for Breakpoints. There's more to them, like conditional Breakpoints that make debugging a bug so much easier and Watchpoints, but these would make my message way too long.

Of course all of the above-mentioned things can be achieved using appropriate handlers for #halt and add stuff to them or make #halts just ignored at deployment time, but these are also steps that can be forgotten...


Joachim


Am 27.12.17 um 00:26 schrieb Ben Coman:
Hi Andrei,

On 26 December 2017 at 09:51, Andrei Stebakov <lispercat@gmail.com> wrote:
Can I expect that break points in Pharo work in the same way as in Visual Works?
When I set a break point in Pharo (6.1 on Windows), it displays a red dot with an exclamation mark and when I send this message to an object, the debugger doesn't get invoked.��

Sorry I'm not familiar with VisualWorks.����
If I define this method (Pharo 6.1 on Linux)...
�� �� Object >> myTest
�� �� �� �� "Object new myTest"
�� �� �� �� self halt.
�� �� �� �� self inform: 'test'.

then evaluate the comment, a debugger is invoked.

If your example is different, could you explain it in more detail?

cheers -ben


-- 
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel          mailto:jtuchel@objektfabrik.de
Fliederweg 1�� �� �� �� �� �� �� �� �� �� �� �� ��http://www.objektfabrik.de
D-71640 Ludwigsburg                  http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0�� �� �� �� ��Fax: +49 7141 56 10 86 1