[RFA] Fix breakpoint condition that use member variables.

[Daniel Jacobowitz]

On Sat, Mar 22, 2008 at 02:55:42PM +0200, Eli Zaretskii wrote:
> That could surprise the user.  Is it possible to make an additional
> change to look for possible other interpretations of i_ which are
> currently in scope, and display a warning of some kind if such
> possibilities are found?

This is how breakpoint conditions have worked as long as I can
remember: they are evaluated at the time the breakpoint is hit,
not at the time they are typed.  So whatever they reference has
to be in scope then.

The early parsing is mainly to give early warning if something
doesn't parse.

-- 
Daniel Jacobowitz
CodeSourcery