From: Yao Qi <yao@codesourcery.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] Use Doxygen for internals documentation
Date: Mon, 14 Oct 2013 13:20:00 -0000 [thread overview]
Message-ID: <525BEF41.6010807@codesourcery.com> (raw)
In-Reply-To: <525877F6.40001@earthlink.net>
On 10/12/2013 06:13 AM, Stan Shebs wrote:
> This patch is the third and final step in the transition away from the
> old GDB internals manual.
>
I tried this patch, and overall, I like the doc generated by doxygen.
>
> To try it out, install doxygen, apply this patch to GDB, configure in
> the usual way, then do
>
> make doxy
>
> in the doc objdir. This will produce a "doxy" subdir, with three
> subdirs in turn, each based on a different config file:
>
> doxy/gdb-api - GDB's "API", basically what is in .h files
> doxy/gdb-xref - the full xref, voluminous
Any reason to produce both of them? I'd like to have a single one.
> doxy/gdbserver - GDBserver xref
> doxy/xml - XML version, for further script-crunching
Do you have an example that these xml files can be consumed by other tools?
>
> To see how the annotations work, look down through minsyms.h and
> utils.h, you can see the comments attached to declarations.
>
> types, see what is used and what is not used.
>
> So I think it's worth going ahead and introducing. But of course
> something like this only works if everybody signs on, patches are
> required to have Doxygen annotations for header file additions, and
> so forth. Look at the header file changes, try noodling around the
> Doxygen output, see if you're willing to be looking at all this for
> the next N years.
>
With this change, we need to write comments in a new way for doxygen. I
go through your patch to minsyms.h, and think the comment style looks
fine to me.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-10-14 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 22:13 Stan Shebs
2013-10-14 13:20 ` Yao Qi [this message]
2013-10-15 23:39 ` Stan Shebs
2013-10-16 17:28 ` Tom Tromey
2013-10-16 19:52 ` Stan Shebs
2013-10-17 20:23 ` Tom Tromey
2013-11-01 11:18 ` Pedro Alves
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=525BEF41.6010807@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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