Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Simon Marchi <simon.marchi@efficios.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] Remove some trivial TYPE_* macros
Date: Thu, 19 Mar 2026 08:34:12 -0600	[thread overview]
Message-ID: <87y0jnanx7.fsf@tromey.com> (raw)
In-Reply-To: <87jyvb7l0a.fsf@redhat.com> (Andrew Burgess's message of "Mon, 16 Mar 2026 17:16:21 +0000")

>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:

Andrew> Simon Marchi <simon.marchi@efficios.com> writes:
>> Here is another small batch of TYPE_* macro removal patches.  I think
>> that these are simple enough, I'd like to them out of the way first.

Andrew> I'm happy to see these macros go.  Hopefully in the future we'll start
Andrew> making some more of these type fields private and provide read only
Andrew> getters where that makes sense.

+1 to that.  Ideally we'd use separate subclasses as well but that is a
bit tricky due to type smashing.

Tom

      parent reply	other threads:[~2026-03-19 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 14:25 Simon Marchi
2026-03-16 14:25 ` [PATCH 1/6] gdb: remove INIT_NONE_SPECIFIC Simon Marchi
2026-03-16 14:25 ` [PATCH 2/6] gdb: remove TYPE_MAIN_TYPE Simon Marchi
2026-03-16 14:25 ` [PATCH 3/6] gdb: remove TYPE_POINTER_TYPE Simon Marchi
2026-03-16 14:25 ` [PATCH 4/6] gdb: remove TYPE_REFERENCE_TYPE Simon Marchi
2026-03-16 14:25 ` [PATCH 5/6] gdb: remove TYPE_RVALUE_REFERENCE_TYPE Simon Marchi
2026-03-16 14:25 ` [PATCH 6/6] gdb: remove TYPE_CHAIN Simon Marchi
2026-03-16 17:16 ` [PATCH 0/6] Remove some trivial TYPE_* macros Andrew Burgess
2026-03-16 17:28   ` Simon Marchi
2026-03-19 14:34   ` Tom Tromey [this message]

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=87y0jnanx7.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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