Re: [PATCH] MI: lvalues and variable_editable

[Nick Roberts <nickrob at snap dot net dot nz>]

 > >  >                                                                    GDB,
 > >  > as it stands, allows you to create a variable object in any frame, and
 > >  > your patch does not work with that. So, either creating variable
 > >  > objects in any frame should be disallowed,
 > > 
 > > Actually I think that would be a good idea.  Generally a user would create
 > > a watch expression in the frame he's examining.  If not, the frontend
 > > would have to prompt for the frame.  Does KDevelop do this?
 > 
 > If you have a GUI with a stack pane, it may be showing a lot of frames
 > at once.  Why force the front end to select a frmae before creating
 > the varobj?

For a start -stack-list-frames (unlike `bt') doesn't list arguments or locals
so you couldn't create such a watch expression with a single mouse click.  But
I'm not suggesting removing such functionality, and we're moving away from the
original focus which was the submission of a patch with differentiates more
clearly between the editable and changeable properties of variable objects.

-- 
Nick                                           http://www.inet.net.nz/~nickrob