Re: [Patch] Fix for -var-update to use natural format to compare

[Daniel Jacobowitz <drow@false.org>]

On Tue, Jan 22, 2008 at 08:49:53PM +0300, Vladimir Prus wrote:
> It's good to improve docs in this way. It should be noted that this
> might not be true in future, say when we add Python scripting,  or
> (maybe) when we'll add a way to specify floating point precision.

Let's keep the documentation focused on what's true today - no point
saying "this might not work someday" when there isn't an alternative
yet.

> > Also, if GDB requires this of frontends showing mutliple formats, it would
> > be nice to have -var-evaluate-expression take a format as an optional
> > parameter.  Then, the frontend would not need to use -var-set-format
> > to get a different formatted value, and could keep the variable object
> > in the natural format at all times.
> > 
> > I can provide a patch if this is a supported idea.
> 
> I personally think this is a good idea! It means that if we for example 
> need to quickly show some value in specific format, like hex value in tooltip,
> we don't need two format setting commands before and after. So, such
> a patch will be valuable independently of how -var-update operates.

I think this is a good idea too.

-- 
Daniel Jacobowitz
CodeSourcery