public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/3] Support template lookups in strncmp_iw_with_mode
Date: Thu, 09 Dec 2021 21:40:29 +0200	[thread overview]
Message-ID: <83czm5tvma.fsf@gnu.org> (raw)
In-Reply-To: <20211209191750.2601228-4-keiths@redhat.com> (message from Keith Seitz via Gdb-patches on Thu, 9 Dec 2021 11:17:50 -0800)

> Date: Thu,  9 Dec 2021 11:17:50 -0800
> From: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
> 
>  gdb/NEWS                                    |   4 +
>  gdb/cp-support.c                            |   8 +-
>  gdb/doc/gdb.texinfo                         |  46 +++
>  gdb/testsuite/gdb.cp/templates.cc           |  47 +++
>  gdb/testsuite/gdb.cp/templates.exp          |  67 +++
>  gdb/testsuite/gdb.linespec/cpcompletion.exp | 437 +++++++++++++++++++-
>  gdb/testsuite/gdb.linespec/cpls-ops.exp     |  53 ++-
>  gdb/testsuite/gdb.linespec/cpls.cc          | 110 ++++-
>  gdb/utils.c                                 |  82 +++-
>  gdb/utils.h                                 |   7 +-
>  10 files changed, 821 insertions(+), 40 deletions(-)

Thanks.

I find the documentation of this feature hard to understand.  I didn't
understand what this does until I've read all of the new text,
including the examples, twice.

I think the documentation could be a lot more self-explanatory if the
part about ignoring the template parameters were mentioned much
earlier.

> +* C++ developers may now ignore template parameter lists when specifying
> +  locations, e.g., while setting breakpoints.  This is analogous to how
> +  completion and symbol lookup handle overloaded functions or ABI tags.

This could be more clear if it described the GDB behavior, not what
GDB users can do due to changes in the GDB behavior.

  reply	other threads:[~2021-12-09 19:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 19:17 C++ template completion support v3 Keith Seitz
2021-12-09 19:17 ` [PATCH v3 1/3] Move find_toplevel_char to cp-support.[ch] Keith Seitz
2021-12-09 19:17 ` [PATCH v3 2/3] Unit tests for strncmp_iw_with_mode Keith Seitz
2021-12-09 19:17 ` [PATCH v3 3/3] Support template lookups in strncmp_iw_with_mode Keith Seitz
2021-12-09 19:40   ` Eli Zaretskii [this message]
2021-12-10 20:54     ` Keith Seitz
2022-02-18 20:34 ` C++ template completion support v3 Tom Tromey
2022-02-24 17:47   ` Keith Seitz
2022-02-24 21:33     ` Tom Tromey
2022-02-25  0:49       ` Keith Seitz

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=83czm5tvma.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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).