I use break on entry often because I do not like the method versions being
cluttered with "halt versions".

Unfortunately the #breaks are slipping in anyway, when I then edit the code
in the debugger and forget about the break. :-(

A confirmation dialog would be nice if a wrapped method is saved and the
break is still in the source.

Am 31.03.2017 15:47 schrieb "Bert Freudenberg" <bert at freudenbergs.de>:

> On Thu, Mar 30, 2017 at 12:01 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
>
>>
>> > On 29.03.2017, at 23:56, Levente Uzonyi <leves at caesar.elte.hu> wrote:
>> >
>> > Inserting `self half` is still superior.
>>
>> If i want to half myself, sure ;)
>>
>> Well, I'd say, it depends. If I'm just exploring the system and dont want
>> to change it, I typically use break on enty.
>>
>
> I'd like to have proper breakpoints that are as convenient as "self halt"
> but don't modify the method source.
>
> - Bert -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170403/fb324e40/attachment.html>