Re: set print object on should affect MI varobjs (PR mi/13393)

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 30 Mar 2012 23:26:48 +0300
> From: xgsa <xgsa@yandex.ru>
> CC: gdb-patches@sourceware.org
> 
> >> +would be printed by the @value{GDBN} CLI.  Note that if
> >> +@samp{set print object} setting is set the @emph{actual} (derived) type
> >> +of the object is set rather than @emph{declared} one.
> > "setting is set" is not right.  I actually don't understand what you
> > tried to say; if you explain your intent, I will suggest a better
> > wording.
> I meant that "set print object on/off" will also affect the "type" field 
> returned by -var-create and -var-list-children.
> Probably, it should be an "option" not "setting". The result will look 
> like this:
> 
> +would be printed by the @value{GDBN} CLI.  Note that if
> +@samp{set print object} option is set the @emph{actual} (derived) type
> +of the object is set rather than @emph{declared} one.
> 
> 
> Is it ok?

Close, but not quite there yet.  The last piece we need to clarify is
the "actual (derived) type of the object is set" part.  What do you
mean by "type is set"?  This text describes the result returned by
'-var-create', so did you mean to say that the actual type is
mentioned in the tuple returned by this operation?  IOW, did you mean
to point out that the 'type=TYPE' part of -var-create's output will
mention the actual type as TYPE?

Thanks.