Sept. 13, 2014
8:54 a.m.
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