Hello, #break has been removed from Pharo4 as we will move to use Refelectivity meta-links for breakpoints (meta annotation on the AST level, not source visible).
On 13 Sep 2014, at 10:54, Johan Brichau <[email protected]> wrote: > Hi guys, > > As described in this issue on the Seaside tracker [1], it appears that > setting a breakpoint on a method simply sends the #break message. > As #break is not an uncommon method name, the choice for this makes is a > de-facto reserved method in Pharo. > > Would it not be better to rename #break to #_break ? This will avoid > unintended clashes. > > Johan > > [1] https://code.google.com/p/seaside/issues/detail?id=829
