From: Jim Blandy <jimb@codesourcery.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: bauerman@br.ibm.com, gary@intrepid.com, gdb@sourceware.org
Subject: Re: GDB in C++
Date: Wed, 11 Jul 2007 20:41:00 -0000 [thread overview]
Message-ID: <m34pkabrmg.fsf@codesourcery.com> (raw)
In-Reply-To: <18069.13868.365370.13474@pkoning-laptop.equallogic.com> (Paul Koning's message of "Wed, 11 Jul 2007 15:57:32 -0400")
Paul Koning <pkoning@equallogic.com> writes:
>>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
>
> Thiago> On Tue, 2007-07-03 at 12:09 -0700, Gary Funck wrote:
> >> If C++ isn't the answer, and keeping all of GDB in "C" is a fixed
> >> point, what changes would the developers recommend that would
> >> offer similar (perceived) improvements in understandability and
> >> extensibility?
>
> Thiago> Speaking as a newcomer who's trying to grasp GDB code, I
> Thiago> think you made very good points. IMHO having reasonable
> Thiago> internals documentation is a very good way to give an
> Thiago> overview of GDB's organization and pitfalls.
>
> Yes.
>
> Thiago> If GDB Internal's contents was transferred to the GDB wiki,
> Thiago> maybe people would feel more compelled to update and expand
> Thiago> it. I know I would try to contribute to it as I learn new
> Thiago> stuff.
>
> Excellent suggestion!
We have a GDB wiki: http://sourceware.org/gdb/wiki/
I wouldn't object to moving the internals documentation there.
High-level organization is pretty key to effective documentation,
though, so the wiki would need aggressive gardening. It would
probably be good for it to have an appointed editor, to avoid ending
up with two or three competing theories for the overall organization.
next prev parent reply other threads:[~2007-07-11 20:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 14:56 Michael Eager
2007-07-01 20:54 ` Daniel Jacobowitz
2007-07-02 1:33 ` Joel Brobecker
2007-07-03 3:49 ` Michael Eager
2007-07-03 7:55 ` Mark Kettenis
2007-07-11 21:04 ` Jan Kratochvil
2007-07-02 7:21 ` Mark Kettenis
2007-07-03 3:57 ` Michael Eager
2007-07-03 7:03 ` Fabian Cenedese
2007-07-03 12:14 ` Robert Dewar
2007-07-03 19:09 ` Gary Funck
2007-07-11 19:47 ` Thiago Jung Bauermann
2007-07-11 19:59 ` Paul Koning
2007-07-11 20:41 ` Jim Blandy [this message]
2007-07-11 21:00 ` Gary Funck
2007-07-11 21:32 ` Daniel Jacobowitz
2007-07-11 21:38 ` Robert Dewar
2007-07-12 3:16 ` Eli Zaretskii
2007-07-12 2:24 ` Michael Eager
2007-07-13 20:21 ` Thiago Jung Bauermann
2007-07-13 20:55 ` Eli Zaretskii
2007-07-13 21:24 ` Thiago Jung Bauermann
2007-07-12 3:11 ` Eli Zaretskii
2007-07-11 21:11 ` Gary Funck
2007-07-02 20:21 ` David Daney
2007-07-02 20: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=m34pkabrmg.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=bauerman@br.ibm.com \
--cc=gary@intrepid.com \
--cc=gdb@sourceware.org \
--cc=pkoning@equallogic.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