Re: MI floating varobj of invalid value

Eli Zaretskii wrote:

>> From: Vladimir Prus <vladimircodesourcery.com>
>> Date: Sun, 27 Apr 2008 01:27:48 +0400
>> 
>> However, if frontend tries to create varobj for
foo
>> at the first stop, and 'foo' is not in scope, then
varobj will not be created.
> 
> Why is that?

For no other reason than "implementation behaves this
way".

> Since a floating varobj's expression is re-parsed every

> time, you should be able to delay parsing and not fail
creation
> because some of its terms are not in scope, right?

Right, that's my reasoning.

- Volodya