From: Simon Marchi <simon.marchi@polymtl.ca>
To: Lancelot SIX <lsix@lancelotsix.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/4] gdb: Add typesafe getter/setter for cmd_list_element.var
Date: Tue, 10 Aug 2021 08:22:31 -0400 [thread overview]
Message-ID: <2cc82d64-f2bd-1e7b-e91c-2b930a8dc75c@polymtl.ca> (raw)
In-Reply-To: <20210808192302.3768766-2-lsix@lancelotsix.com>
I'm forwarding some comments from Tony Tye, from AMD, who looked at the
patch, and had some minor comments.
> @@ -230,7 +226,7 @@ struct cmd_list_element
>
> /* Pointer to variable affected by "set" and "show". Doesn't
> matter if type is not_set. */
> - void *var = nullptr;
> + setting var;
The comment should probably be updated, this is no longer a pointer.
Well, for now it contains a pointer, but later in the series it can
become a getter/setter too. So maybe just say "Setting affected by
...".
> diff --git a/gdb/command.h b/gdb/command.h
> index baf34401a07..644812c4d46 100644
> --- a/gdb/command.h
> +++ b/gdb/command.h
> @@ -125,6 +125,164 @@ typedef enum var_types
> }
> var_types;
>
> +/* Return true if a setting of type VAR_TYPE is backed with type T.
> +
> + This function is left without definition intentionally. This template
> + is specialized for all valid types that are used to back var_types.
> + Therefore if one tries to instantiate this un-specialized template it
> + means the T parameter is not a type used to back a var_type and it is most
> + likely a programming error. */
> +template<typename T>
> +inline bool var_type_uses (var_types t);
So what will happen if you try to use var_type_uses with an invalid
template type, link error? Tony suggested using a static_assert to have
a compile-time error instead, with an explanation. I suppose you would
define a body for this function and put a static_assert (false) in
there?
Simon
next prev parent reply other threads:[~2021-08-10 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 19:22 [PATCH v2 0/4] gdb: Refactor cmd_list_element.var Lancelot SIX
2021-08-08 19:22 ` [PATCH v2 1/4] gdb: Add typesafe getter/setter for cmd_list_element.var Lancelot SIX
2021-08-10 1:29 ` Simon Marchi
2021-08-10 12:22 ` Simon Marchi [this message]
2021-08-10 21:58 ` Lancelot SIX
2021-08-11 0:56 ` Simon Marchi
2021-08-08 19:23 ` [PATCH v2 2/4] gdb: make string-like set show commands use std::string variable Lancelot SIX
2021-08-08 19:23 ` [PATCH v2 3/4] gdb: Have setter and getter callbacks for settings Lancelot SIX
2021-08-10 3:01 ` Simon Marchi
2021-08-10 22:18 ` Lancelot SIX
2021-08-11 1:01 ` Simon Marchi
2021-08-11 20:00 ` Lancelot SIX
2021-08-19 21:03 ` Simon Marchi
2021-08-20 7:04 ` Lancelot SIX
2021-08-08 19:23 ` [PATCH v2 4/4] gdb: Setting setter return a bool to tell if the value changed Lancelot SIX
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=2cc82d64-f2bd-1e7b-e91c-2b930a8dc75c@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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).