From: Yao Qi <yao@codesourcery.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Use Doxygen for internals documentation
Date: Fri, 07 Feb 2014 13:29:00 -0000 [thread overview]
Message-ID: <52F4DF1B.9070100@codesourcery.com> (raw)
In-Reply-To: <52F420E0.9050203@earthlink.net>
Stan,
I applied this patch and run 'make doxy' in dir doc. It looks good!
On 02/07/2014 07:55 AM, Stan Shebs wrote:
> +<p>
> +These are primarily useful for people working on GDB itself. Users of
> +GDB, people working with stubs, and people working on frontends to GDB
> +are all better served by the GDB manual, which is the official
> +definition for all of GDB's external interfaces.
We may add a link to GDB manual.
> diff --git a/gdb/doc/filter-for-doxygen b/gdb/doc/filter-for-doxygen
> new file mode 100755
> index 0000000..457d088
> --- /dev/null
> +++ b/gdb/doc/filter-for-doxygen
> @@ -0,0 +1,14 @@
> +#!/bin/sh
> +
Missing copyright header?
> +# This filters GDB source before Doxygen can get confused by it;
> +# this script is listed in the doxyfile. The output is not very
> +# pretty, but at least we get output that Doxygen can understand.
> +#
> +# $1 is a source file of some kind. The source we wish doxygen to
> +# process is put on stdout.
> +
> +# (Adapted from gcc/contrib/filter_gcc_for_doxygen)
> +
> +dir=`dirname $0`
> +perl $dir/filter-params.pl < $1
> +exit 0
> diff --git a/gdb/doc/filter-params.pl b/gdb/doc/filter-params.pl
> new file mode 100644
> index 0000000..eedcc5b
> --- /dev/null
> +++ b/gdb/doc/filter-params.pl
> @@ -0,0 +1,11 @@
> +#!/usr/bin/perl
> +
Likewise.
> +# This Perl script tweaks GDB sources to be more useful for Doxygen.
> +
> +while (<>) {
> + # Allow "/* * " as an equivalent to "/** ", better for Emacs compat.
> + s/^\/\* \* /\/** /sg;
> + # Manually expand macro seen in structs and such.
> + s/ENUM_BITFIELD[ \t]*\((.*?)\)/__extension__ enum $1/sg;
Why do we need this substitution here? Anything wrong if we don't do
the substitution? I don't recall this was asked in last review.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-02-07 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 23:55 Stan Shebs
2014-02-07 13:29 ` Yao Qi [this message]
2014-02-07 15:36 ` Ludovic Courtès
2014-02-07 16:18 ` Eli Zaretskii
2014-02-08 9:59 ` Sergio Durigan Junior
2014-02-08 16:54 ` Ludovic Courtès
2014-02-08 5:27 ` Doug Evans
2014-02-11 19:08 ` Stan Shebs
2014-02-11 19:19 ` Mark Kettenis
2014-02-11 19:28 ` Eli Zaretskii
2014-02-11 19:52 ` Stan Shebs
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=52F4DF1B.9070100@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