[squeak-dev] Squeak 6 kernel changes, ContextPart+MethodContext -> Context

Tobias Pape Das.Linux at gmx.de
Wed Mar 29 22:01:51 UTC 2017


> 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.

> 
> Levente
> 
> On Wed, 29 Mar 2017, Tobias Pape wrote:
> 
>> 
>>> On 29.03.2017, at 23:43, Levente Uzonyi <leves at caesar.elte.hu> wrote:
>>> The one which allows you to break at any instruction. There is "toggle break on entry", which does nothing but recompile your method with `self break` at the start. I find that feature hardly useful.
>> 
>> Well, there's WrappedBreakpoint, which can do that without recompiling…
>> 
>>> Levente
>>> On Wed, 29 Mar 2017, Tobias Pape wrote:
>>>>> On 29.03.2017, at 23:16, Levente Uzonyi <leves at caesar.elte.hu> wrote:
>>>>> On Wed, 29 Mar 2017, Eliot Miranda wrote:
>>>>>> Hi All,
>>>>>>  another change planned for Squeak 6 is eliminating ContextPart & MethodContext in favor of Context.  In reviewing the (very few) changes
>>>>>> necessary I came across the following:
>>>>>> MethodContext>>printString
>>>>>> "Answer an emphasized string in case of a breakpoint method"
>>>>>> ^(self method notNil and: [self method hasBreakpoint])
>>>>>> ifTrue:[(super printString , ' [break]') asText allBold]
>>>>>> ifFalse:[super printString] Seriously?  I don't object to modifying [Method]Conext>>printOn: to include [break] but having printString answer a text seems completely broken
>>>>>> to me, and overriding printString is a hack; printOn: being the operative method for producing self-descriptions.  Should we nuke it and add
>>>>>> [break] to printOn:? Or...?
>>>>> Nuke it. AFAIK breakpoints never worked.
>>>> which?
>>>>> Levente
>>>>>> _,,,^..^,,,_
>>>>>> best, Eliot
> 



More information about the Squeak-dev mailing list