Re: [MI] lvalues and variable_editable

[Vladimir Prus <ghost@cs.msu.su>]

Daniel Jacobowitz wrote:

> On Mon, Jul 09, 2007 at 05:51:42PM +1200, Nick Roberts wrote:
>> (Me)
>> 
>>  > Anyway let me submit a more complete patch, in due course, for
>>  > consideration after the release.
>> 
>> This is what I have in mind.  There are no regressions, at least with MI
>> (I
>> can't test Insight).  If there's still time, this could go in before the
>> branch.  I also have a (much smaller) change, that I've submitted
>> earlier, for after the release which adds the editable field to the
>> output of -var-create and -var-list-children, .
> 
> Thanks for doing this.  I have two questions for you.
> 
> - Why do variable_editable_p and varobj_value_is_changeable_p have to
> be different?  That is, do we need varobj_value_is_changeable_p to be
> true for any non-lvals.  If not, we can eliminate one of them.

I would expect being able to create varobj for "a + b" and have it
updated as I step, and being not editable. So variable_editable_p will
be false, whereas varobj_value_is_changeable_p will be true.

- Volodya