From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: [commit] Do not rely on FIELD_LOC_KIND_BITPOS being zero
Date: Tue, 17 Apr 2012 14:11:00 -0000 [thread overview]
Message-ID: <20120417140535.GA5996@host2.jankratochvil.net> (raw)
In-Reply-To: <4F8D783C.3000501@redhat.com>
On Tue, 17 Apr 2012 16:03:40 +0200, Pedro Alves wrote:
> You're deeply confused if you think C++ invented getters/setters.
I never thought so and I never said so. But C++ is the most easily applicable
getters/setters-featuring language to GDB.
Jan
next prev parent reply other threads:[~2012-04-17 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 12:52 Jan Kratochvil
2012-04-17 13:09 ` Pedro Alves
2012-04-17 13:57 ` Jan Kratochvil
2012-04-17 13:59 ` Pedro Alves
2012-04-17 14:03 ` Jan Kratochvil
2012-04-17 14:05 ` Pedro Alves
2012-04-17 14:11 ` Jan Kratochvil [this message]
2012-04-17 14:12 ` Pedro Alves
2012-04-17 14:16 ` Jan Kratochvil
2012-04-17 14:48 ` Tom Tromey
2012-04-17 14:52 ` Joel Brobecker
2012-04-17 14:27 ` 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=20120417140535.GA5996@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=siddhesh@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