public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 04/11] Remove #if HAVE_PYTHON
Date: Tue, 21 Jan 2014 20:44:00 -0000	[thread overview]
Message-ID: <52DEDC30.7060404@redhat.com> (raw)
In-Reply-To: <1385258996-26047-5-git-send-email-yao@codesourcery.com>

On 11/23/2013 06:09 PM, Yao Qi wrote:
> This patch removes some unnecessary "#if HAVE_PYTHON" so that more
> code is generalized.

Yippie! :-)

This all looks good to me.

Keith

> 2013-11-24  Pedro Alves  <pedro@codesourcery.com>
> 	    Yao Qi  <yao@codesourcery.com>
>
> 	* varobj.c: Remove "#if HAVE_PYTHON" and "#endif".
> 	(varobj_get_iterator): Wrap up code for pretty-printer by
> 	"#if HAVE_PYTHON" and "#endif".
> 	(update_dynamic_varobj_children): Likewise.
> ---
>   gdb/varobj.c |   20 +++++---------------
>   1 files changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/gdb/varobj.c b/gdb/varobj.c
> index 28e934c..e362229 100644
> --- a/gdb/varobj.c
> +++ b/gdb/varobj.c
> @@ -212,13 +212,9 @@ static char *my_value_of_variable (struct varobj *var,
>
>   static int is_root_p (struct varobj *var);
>
> -#if HAVE_PYTHON
> -
>   static struct varobj *varobj_add_child (struct varobj *var,
>   					struct varobj_item *item);
>
> -#endif /* HAVE_PYTHON */
> -
>   /* Private data */
>
>   /* Mappings of varobj_display_formats enums to gdb's format codes.  */
> @@ -701,8 +697,6 @@ varobj_restrict_range (VEC (varobj_p) *children, int *from, int *to)
>       }
>   }
>
> -#if HAVE_PYTHON
> -
>   /* A helper for update_dynamic_varobj_children that installs a new
>      child when needed.  */
>
> @@ -747,6 +741,8 @@ install_dynamic_child (struct varobj *var,
>       }
>   }
>
> +#if HAVE_PYTHON
> +
>   static int
>   dynamic_varobj_has_child_method (struct varobj *var)
>   {
> @@ -762,6 +758,7 @@ dynamic_varobj_has_child_method (struct varobj *var)
>     do_cleanups (back_to);
>     return result;
>   }
> +#endif
>
>   /* Dynamic varobj's iterator factory.  Returns an iterator object
>      suitable for iterating over VAR's children.  */
> @@ -769,8 +766,10 @@ dynamic_varobj_has_child_method (struct varobj *var)
>   static struct varobj_iter *
>   varobj_get_iterator (struct varobj *var)
>   {
> +#if HAVE_PYTHON
>     if (var->dynamic->pretty_printer)
>       return py_varobj_get_iterator (var, var->dynamic->pretty_printer);
> +#endif
>
>     gdb_assert_not_reached (_("\
>   requested an interator from a non-dynamic varobj"));
> @@ -788,7 +787,6 @@ varobj_clear_saved_item (struct varobj_dynamic *var)
>         var->saved_item = NULL;
>       }
>   }
> -#endif
>
>   static int
>   update_dynamic_varobj_children (struct varobj *var,
> @@ -801,7 +799,6 @@ update_dynamic_varobj_children (struct varobj *var,
>   				int from,
>   				int to)
>   {
> -#if HAVE_PYTHON
>     int i;
>
>     *cchanged = 0;
> @@ -891,9 +888,6 @@ update_dynamic_varobj_children (struct varobj *var,
>     var->num_children = VEC_length (varobj_p, var->children);
>
>     return 1;
> -#else
> -  gdb_assert_not_reached ("should never be called if Python is not enabled");
> -#endif
>   }
>
>   int
> @@ -970,8 +964,6 @@ varobj_list_children (struct varobj *var, int *from, int *to)
>     return var->children;
>   }
>
> -#if HAVE_PYTHON
> -
>   static struct varobj *
>   varobj_add_child (struct varobj *var, struct varobj_item *item)
>   {
> @@ -983,8 +975,6 @@ varobj_add_child (struct varobj *var, struct varobj_item *item)
>     return v;
>   }
>
> -#endif /* HAVE_PYTHON */
> -
>   /* Obtain the type of an object Variable as a string similar to the one gdb
>      prints on the console.  */
>
>

  reply	other threads:[~2014-01-21 20:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24  5:04 [RCF 00/11] Visit varobj available children only in MI Yao Qi
2013-11-24  2:12 ` [PATCH 07/11] MI option --available-children-only Yao Qi
2014-01-21 20:45   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 10/11] Match dynamic="1" in the output of -var-list-children Yao Qi
2014-01-21 20:47   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 03/11] Iterate over 'struct varobj_item' instead of PyObject Yao Qi
2014-01-21 20:44   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 04/11] Remove #if HAVE_PYTHON Yao Qi
2014-01-21 20:44   ` Keith Seitz [this message]
2013-11-24  2:12 ` [PATCH 09/11] Delete varobj's children on traceframe is changed Yao Qi
2014-01-21 20:47   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 05/11] Rename varobj_pretty_printed_p to varobj_is_dynamic_p Yao Qi
2014-01-21 20:44   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 11/11] Test case Yao Qi
2014-01-21 20:49   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 06/11] Use varobj_is_dynamic_p more widely Yao Qi
2014-01-21 20:44   ` Keith Seitz
2013-11-24  2:12 ` [PATCH 02/11] Generalize varobj iterator Yao Qi
2014-01-21 20:44   ` Keith Seitz
2014-01-22  1:07     ` Doug Evans
2013-11-24  2:12 ` [PATCH 01/11] Use 'struct varobj_item' to represent name and value pair Yao Qi
2014-01-21 20:43   ` Keith Seitz
2014-01-22  1:00     ` Doug Evans
2014-01-23  4:08       ` Yao Qi
2014-01-23 16:08         ` Doug Evans
2013-11-24  2:12 ` [PATCH 08/11] Iterator varobj_items by their availability Yao Qi
2014-01-21 20:46   ` Keith Seitz
2013-12-02  9:09 ` [RCF 00/11] Visit varobj available children only in MI Yao Qi
2013-12-17 12:54 ` Yao Qi
2014-01-07 18:22 ` Keith Seitz
2014-01-08 11:41   ` Joel Brobecker
2014-01-08 14:27   ` 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=52DEDC30.7060404@redhat.com \
    --to=keiths@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).