2009/1/26 Damien Cassou <[email protected]>: > On Mon, Jan 26, 2009 at 7:17 PM, Mariano Martinez Peck > <[email protected]> wrote: >> Igor: Sorry not beeing able to help you. I am still learning squeak. >> However, I would really like conditional breakpoints. I found them very >> useful in Eclipse IDE. Let me know if you could get them working. > > What about #haltIf:? That's already useful. >
here, i'm speaking about setting breakpoints using UI i.e. without changing the method. I wrote a simple OB-based breakpoint manager, where you can edit breakpoints list and possibly set a condition to break. Of course, you can always put 'wand isZapped ifTrue: [self halt]' in any method, but this having one huge drawback: once you modify the method, a change is recorded into .changes, as well as many other parts of the system get notified about such change. But we don't want to mark packages modified, nor unnecessary pollute .changes file only because we need to test some functionality (by putting a breakpoint), right? Because such practice makes harder to manage the source code (you forced to always get back to places where you put the halt to remove it, and this is a bit annoying). > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
