Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFAv2 3/6] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]
Date: Tue, 18 Sep 2018 15:52:00 -0000	[thread overview]
Message-ID: <874lemu7kz.fsf@tromey.com> (raw)
In-Reply-To: <20180826165359.1600-4-philippe.waroquiers@skynet.be> (Philippe	Waroquiers's message of "Sun, 26 Aug 2018 18:53:56 +0200")

>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:

Philippe>   As stack.h now uses a type defined in gdb_regex.h, all files including stack.h
Philippe>   need to include gdb_regex.h.

It's better to just include gdb_regex.h from stack.h in this situation.

Philippe> +	  if (preg

I think preg.has_value ().  gdb is trending away from these bool
conversions, I think.  At least that's been the style for pointers.

Philippe> +	  if (treg

Here too.

Philippe> +/* Prepares the regular expression REG from REGEXP.
Philippe> +   If REGEXP is NULL, it results in an empty regular expression.  */
Philippe> +static void
Philippe> +prepare_reg (const char *regexp, gdb::optional<compiled_regex> &reg)

Out parameters should be pointers in the gdb style.

Philippe> -  iterate_over_block_local_vars (block,
Philippe> +  iterate_over_block_local_vars (block, preg, treg,
Philippe>  				 do_print_variable_and_value,
Philippe>  				 &cb_data);

iterate_over_block_local_vars already takes some opaque data that it
just passes through to the callback.  So, I think there should not be
a need to add the regexp parameters directly to it.  Instead they can be
put into the cb_data here.

Philippe>  void
Philippe>  iterate_over_block_arg_vars (const struct block *b,
Philippe> +			     const gdb::optional<compiled_regex> &preg,
Philippe> +			     const gdb::optional<compiled_regex> &treg,
Philippe>  			     iterate_over_block_arg_local_vars_cb cb,
Philippe>  			     void *cb_data)

Same here.

Philippe> +/* Returns true if the type_name of symbol_type of SYM matches TREG.
Philippe> +   If SYM has no symbol_type or symbol_name, returns false.  */
Philippe> +
Philippe> +bool
Philippe> +treg_matches_sym_type_name (const compiled_regex &treg,
Philippe> +			    const struct symbol *sym)
Philippe> +{
Philippe> +  if (language_mode == language_mode_auto)
Philippe> +    language_def (SYMBOL_LANGUAGE (sym))->la_print_type
Philippe> +      (sym_type, "", &printed_sym_type_name,
Philippe> +       -1, 0, &default_ptype_flags);

I think this won't actually work, because the type printing code is free
to use current_language.  This is not good, but it is how it is.

So instead I think what this should do is save and restore the current
language.  IIRC there's a helper RAII class for that already.

Then you can just call type_print and drop patch #2.

Philippe> +extern bool
Philippe> +treg_matches_sym_type_name (const compiled_regex &treg,
Philippe> +			    const struct symbol *sym);
 
No newline after the "bool" for a declaration.

Tom


  reply	other threads:[~2018-09-18 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 16:54 [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 3/6] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables] Philippe Waroquiers
2018-09-18 15:52   ` Tom Tromey [this message]
2018-09-23 21:34     ` Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 4/6] Document changes " Philippe Waroquiers
2018-08-26 18:19   ` Eli Zaretskii
2018-08-26 16:54 ` [RFAv2 2/6] Make struct type_print_options default_ptype_flags non static Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 1/6] New cli-utils.h/.c function extract_info_print_args Philippe Waroquiers
2018-09-18 15:31   ` Tom Tromey
2018-09-23 20:16     ` Philippe Waroquiers
2018-09-24 13:07       ` Tom Tromey
2018-09-25  4:37         ` Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 6/6] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 5/6] Announce changes in NEWS to info [args|functions|locals|variables] Philippe Waroquiers
2018-08-26 18:21   ` Eli Zaretskii
2018-08-27  4:39     ` Philippe Waroquiers
2018-08-27 14:59       ` Eli Zaretskii
2018-09-06 20:16 ` PING Re: [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-09-13 19:27 ` PING^2 " Philippe Waroquiers

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=874lemu7kz.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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