This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Ping: frozen variable objects
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sources dot redhat dot com
- Date: Wed, 18 Apr 2007 09:38:17 +0400
- Subject: Re: Ping: frozen variable objects
- References: <200703251351.43195.vladimir@codesourcery.com> <17954.4745.780804.328395@farnswood.snap.net.nz> <ud525jsvh.fsf@gnu.org>
On Monday 16 April 2007 00:16, Eli Zaretskii wrote:
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Sun, 15 Apr 2007 23:54:49 +1200
> > Cc: Eli Zaretskii <eliz@gnu.org>, drow@false.org,
> > gdb-patches@sources.redhat.com
> >
> > > Here's an editorial patch based on comments from you, Dan and Nick. OK?
> >
> > It's Eli who decides, but having -var-update reference -var-set-frozen which in
> > turn references -var-update seems too complicated, and shouldn't be necessary
> > if there was a natural flow.
>
> I'm afraid I wasn't following this sub-thread closely enough, so
> forgive me, Vladimir, if I ask what was already said: could you please
> explain the rationale for your change of the anchors in this patch?
You've asked to add a reference to -var-update. There was already -var-update
anchor. However, that anchor was pointing in the middle of -var-update documentaiton,
so following the reference would land the reader at list of some attributes, which
would be confusing. And it seems that calling anchor for entire -var-update docs
as -var-update is more reasonable then using -var-update anchor for the list
of fields output by -var-update.
Does this clarify things?
- Volodya