[Pharo-project] Writing a conditions for breakpoint

Mariano Martinez Peck marianopeck at gmail.com
Mon Jan 26 16:33:03 EST 2009


>
> 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).
>


+1 100%


>
> > --
> > Damien Cassou
> > http://damiencassou.seasidehosting.st
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project at lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20090126/d6ed5707/attachment-0001.html>


More information about the Pharo-dev mailing list