On Tue, 2008-09-30 at 13:38 +0200, Philippe Marschall wrote:
> 2008/9/25 Randal L. Schwartz <merlyn at stonehenge.com>:
> >>>>>> "David" == David Röthlisberger <squeak at webcitas.ch> writes:
> >
> >>> hh2 at lexdb> In particular: the red flag means that there is a 'self halt' in the method.
> >>> Sadly, it's also true when there's a "break" message sent to anything.
> >>> Which means some of my seaside methods that want a <br> get flagged,
> >>> because they have "html break".
> >
> > David> yeah, this is bad, but unfortunately there is no easy way to avoid that,
> > David> except excluding #break from the list of "dangerous" senders. But this doesn't
> > David> really make sense as it is as important to know if a method sends #break or
> > David> #halt.
> >
> > Maybe the seaside folks can add a new method for #br and deprecate
> > #break or something in 2.9.
> 
> No way. Fix your tools.
> 
I thought that at first, too. But then break is a method
in Object and the seaside stuff changes semantics for that
call. So the decision would be that there is no need for 
setting breakpoints while dealing with the canvases. I
doubt that. 
The funny thing here is that if seaside would remove that
selector, a lot of seaside apps will literally break :))

Norbert