From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Report the main thread.
Date: Sun, 11 May 2008 22:19:00 -0000 [thread overview]
Message-ID: <18471.24734.936595.281750@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200805111845.32141.vladimir@codesourcery.com>
> > > struct thread_info is defined in gdbthread.h. What prevents you from
> > > including that header?
> >
> > I think the idea is not to expose the internals to other parts of the code.
>
> There's nothing in gdbthread.h to indicate that, I think.
It's not specific to gdbthread.h but a general principle. Look at varobj.h.
It just declares struct varobj (without it's members) which means that all
the setters and getters (varobj_set/get_*) need to be defined in varobj.c
for mi-cmd-var.c to access the members. I guess it's a poor man's data
encapsulation.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-05-11 21:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 18:00 Nick Roberts
2008-05-10 19:26 ` Vladimir Prus
2008-05-11 14:10 ` Nick Roberts
2008-05-11 14:45 ` Vladimir Prus
2008-05-11 15:52 ` Nick Roberts
2008-05-11 16:00 ` Vladimir Prus
2008-05-11 16:13 ` Nick Roberts
2008-05-11 16:41 ` Vladimir Prus
2008-05-11 22:19 ` Nick Roberts [this message]
2008-05-12 22:22 ` Michael Snyder
2008-05-11 20:19 ` Joel Brobecker
2008-05-11 21:10 ` Vladimir Prus
2008-05-11 22:33 ` Nick Roberts
2008-05-12 3:18 ` Daniel Jacobowitz
2008-05-12 16:11 ` Nick Roberts
2008-05-12 18:19 ` Daniel Jacobowitz
2008-05-10 19:42 ` Vladimir Prus
2008-05-10 22:12 ` Joel Brobecker
2008-05-11 14:29 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2008-04-26 16:44 Vladimir Prus
2008-04-26 17:16 ` Mark Kettenis
2008-04-26 17:22 ` Daniel Jacobowitz
2008-04-26 17:31 ` Vladimir Prus
2008-04-26 21:05 ` Daniel Jacobowitz
2008-04-26 22:36 ` Vladimir Prus
2008-04-27 4:27 ` Nick Roberts
2008-04-27 9:03 ` Vladimir Prus
2008-04-27 11:14 ` Daniel Jacobowitz
2008-04-27 14:24 ` Nick Roberts
2008-04-27 13:53 ` Nick Roberts
2008-04-27 15:50 ` Daniel Jacobowitz
2008-04-27 16:07 ` Mark Kettenis
2008-04-27 16:07 ` Pedro Alves
2008-04-27 21:46 ` Mark Kettenis
2008-04-28 3:31 ` Pedro Alves
2008-04-27 18:25 ` Daniel Jacobowitz
2008-04-30 10:11 ` Vladimir Prus
2008-04-30 13:28 ` Daniel Jacobowitz
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=18471.24734.936595.281750@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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