From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tui] Factor out tui_noscroll_window et al
Date: Mon, 13 Nov 2023 10:09:47 -0700 [thread overview]
Message-ID: <87msvhtw9w.fsf@tromey.com> (raw)
In-Reply-To: <c95b522b-0f92-4724-aa1e-d642f9fca580@suse.de> (Tom de Vries's message of "Mon, 13 Nov 2023 10:37:23 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Evidently, this introduces multiple inheritance.
Tom> Here ( https://gcc.gnu.org/codingconventions.html#CandCxx ) we read:
FWIW you can't really go by the GCC conventions. GCC is a lot more
conservative about C++ than GDB is.
Tom> I think the newly introduced classes are close enough to the traits
Tom> concept described above for the multiple inheritance to be acceptable.
Makes sense to me. And FWIW GDB already uses multiple inheritance.
Tom
next prev parent reply other threads:[~2023-11-13 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 15:06 Tom de Vries
2023-11-13 9:37 ` Tom de Vries
2023-11-13 17:09 ` Tom Tromey [this message]
2023-11-14 15:02 ` Tom de Vries
2023-11-13 17:08 ` Tom Tromey
2023-11-13 21:03 ` Tom de Vries
2023-11-14 14:13 ` Tom Tromey
2024-02-21 17:32 ` Simon Marchi
2024-02-22 12:07 ` Tom de Vries
2024-02-22 13:13 ` Tom de Vries
2024-02-22 15:07 ` Tom Tromey
2024-02-22 15:26 ` Tom de Vries
2024-02-23 1:39 ` Tom Tromey
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=87msvhtw9w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).