Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 12/12] NEWS and Doc on --available-children-only
Date: Mon, 17 Feb 2014 15:04:00 -0000	[thread overview]
Message-ID: <83zjlp93vz.fsf@gnu.org> (raw)
In-Reply-To: <5301D9F4.5010306@codesourcery.com>

> Date: Mon, 17 Feb 2014 17:44:20 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
> 
> On 02/14/2014 05:40 PM, Eli Zaretskii wrote:
> > This doesn't really say much about the new option, because what
> > "available children" means is not explained at all.  Can you add a
> > sentence about that, or, better, reword this sentence
> > 
> >   When used, only the available children are displayed.
> > 
> > so that the second part explains which children will be displayed and
> > which won't?
> 
> IMO, "available children" is not a new term in GDB.  We've already had
> some in doc:
> 
>   Note that this number is not completely reliable for a dynamic varobj.
>   It will return the current number of children, but more children may
>                                                           ^^^^^^^^^^^^
>   be available.
>   ^^^^^^^^^^^^^
> 
>   The @samp{numchild} field in other varobj responses is generally not
>   valid for a dynamic varobj -- it will show the number of children that
>   @value{GDBN} knows about, but because dynamic varobjs lazily
>   instantiate their children, this will not reflect the number of
>   children which may be available.
>   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

No, that's definitely not the same.  Here, the text just says that not
all children are shown, and "available" is used in its usual meaning.

> "available children" means children, whose values are available, or
> value available children.  How about replacing "available children"
> with "value available children"?  Is it clear?

No, sorry.  "Children whose values are available" is not clear at all.

Can you explain to me what makes the value "available", or what
prevents it from becoming available?  Then I will suggest a suitable
wording.

>  The number of children of the varobj.  This number is not necessarily
>  reliable for a dynamic varobj.  Instead, you must examine the
> -@samp{has_more} attribute.
> +@samp{has_more} attribute.  If the @samp{--available-children-only}
> +option was specified, this number is not reliable either.
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"this number is not reliable for any varobj".

Please also make similar corrections in other places.

The rest of the patch is OK, so we are only left with describing what
are the "value available children".

Thanks.


  reply	other threads:[~2014-02-17 15:04 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  8:46 [RFC 00/12 V2] Visit varobj available children only in MI Yao Qi
2014-02-14  8:46 ` [PATCH 01/12] Use 'struct varobj_item' to represent name and value pair Yao Qi
2014-04-23 18:16   ` Keith Seitz
2014-05-21 17:53   ` Tom Tromey
2014-02-14  8:46 ` [PATCH 05/12] Rename varobj_pretty_printed_p to varobj_is_dynamic_p Yao Qi
2014-04-24 17:39   ` Keith Seitz
2014-05-21 18:02   ` Tom Tromey
2014-02-14  8:46 ` [PATCH 07/12] MI option --available-children-only Yao Qi
2014-04-24 20:02   ` Keith Seitz
2014-02-14  8:46 ` [PATCH 08/12] Iterator varobj_items by their availability Yao Qi
2014-04-24 20:28   ` Keith Seitz
2014-02-14  8:46 ` [PATCH 11/12] Test case Yao Qi
2014-04-18 11:45   ` Yao Qi
2014-04-24 20:53     ` Keith Seitz
2014-02-14  8:46 ` [PATCH 04/12] Remove #if HAVE_PYTHON Yao Qi
2014-04-23 19:25   ` Keith Seitz
2014-05-21 17:52   ` Tom Tromey
2014-02-14  8:46 ` [PATCH 06/12] Use varobj_is_dynamic_p more widely Yao Qi
2014-04-24 18:17   ` Keith Seitz
2014-05-21 18:04   ` Tom Tromey
2014-02-14  8:46 ` [PATCH 09/12] Delete varobj's children on traceframe is changed Yao Qi
2014-04-24 20:45   ` Keith Seitz
2014-02-14  8:46 ` [PATCH 10/12] Match dynamic="1" in the output of -var-list-children Yao Qi
2014-04-24 20:50   ` Keith Seitz
2014-02-14  8:46 ` [PATCH 03/12] Iterate over 'struct varobj_item' instead of PyObject Yao Qi
2014-04-23 19:29   ` Keith Seitz
2014-05-21 18:01   ` Tom Tromey
2014-05-23  1:33     ` Yao Qi
2014-06-04 20:22       ` Tom Tromey
2014-02-14  8:46 ` [PATCH 12/12] NEWS and Doc on --available-children-only Yao Qi
2014-02-14  9:40   ` Eli Zaretskii
2014-02-17  9:46     ` Yao Qi
2014-02-17 15:04       ` Eli Zaretskii [this message]
2014-02-18  2:01         ` Yao Qi
2014-02-18  5:11           ` Eli Zaretskii
2014-02-18  7:14             ` Yao Qi
2014-02-18 15:07               ` Eli Zaretskii
2014-02-14  8:46 ` [PATCH 02/12] Generalize varobj iterator Yao Qi
2014-04-23 19:24   ` Keith Seitz
2014-05-21 17:51   ` Tom Tromey
2014-05-23  1:23     ` Yao Qi
2014-06-04 20:21       ` Tom Tromey
2014-06-05  5:36         ` Yao Qi
2014-06-05 18:21           ` Tom Tromey
     [not found] ` <5327A296.3050605@codesourcery.com>
2014-04-04  2:00   ` [RFC 00/12 V2] Visit varobj available children only in MI Yao Qi
2014-04-17  1:12     ` ping : " Yao Qi
2014-04-21 16:20       ` Joel Brobecker
2014-04-22  2:54         ` Yao Qi
2014-06-12  7:37 ` Yao Qi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zjlp93vz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox