Re: [patch] Add an evaluation function hook to Python breakpoints.

[Doug Evans <dje@google.com>]

On Wed, Jan 5, 2011 at 12:23 PM, Phil Muldoon <pmuldoon@redhat.com> wrote:
> Yeah ultimately this was going to be series of patches (the first being
> this, the ability to write conditions entirely within Python), but the
> whole-story (from these threads) has probably shown we need to think
> about the solution in totality, not incrementally.

I don't mind the incremental approach (fwiw).
There is value in having the stop condition being computed in python.
[As long as we have a clear approach to handling old-style condition
(e.g. break foo if bar) vs new python-style condition.]

It breaks down, I think, in using it for some of the things we've
discussed, but that doesn't diminish the utility of stop_p (or however
it's named).

One thing that may require a non-incremental approach is what kind of
class hierarchy (if any) we want for breakpoints.