> Yes... > > I was guilty of harvesting that for 3.7 or 3.6... (Squeak that is).
nobody is guilty (we are not in religious stuff). > > In the Old Browser, you have an entry "toggle break on entry". What this > does is that it compiles a new version of the method (it uses a bit a strange > way of doing that using the old AST...). This version has a self break at the > beginning, > yet points to the old source so you don't see it. > > Now the BreakPointmanager can remove all BreakPoints, all for a class and > things like > that easily. it knows if there is one. CompiledMethod has #hasBreakpoint. > Setting breakpoints > does not invalidate code (as opposed to self halt). > > So there is everything to make a nice UI for it... > > The model is a bit limited. Only break on entry, no probes and so on. But it > works. > The limitations are mostly because everything else is hard to do with the bad > model we have in the current system of doing structural reflection below > method > granularity... > > We should add a nice UI for it *and* soon we can do oh so much better much > easier :-) May be lukas can get inspired and provide some break points support for OB :) For CodeHolder may be somebody else wants to have a look. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
