From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Tue, 27 Oct 2009 10:07:00 -0000 [thread overview]
Message-ID: <200910270717.n9R7H58K006139@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20091012161424.GA20603@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Mon, 12 Oct 2009 18:14:24 +0200)
> X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
> Date: Mon, 12 Oct 2009 18:14:24 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Hi,
>
> currently there is gdb/doc/gdbint.texinfo referencing gdb/ sources functions
> and duplicating various comments in the gdb/*.c sources. At the same time the
> gdb/doc/gdbint.texinfo content is obsolete and one usually misses it when
> dealing with the sources.
>
> May the GDB project start using some tool to format documentation from the
> sources? One could move the appropriate parts of gdb/doc/gdbint.texinfo into
> gdb/*.c along the patches being submitted, keeping in gdb/doc/gdbint.texinfo
> only the abstract parts in the future.
>
> This proposal was already discussed in the past.
I'm not a big fan of this sort od documentation for three reasons:
1. It makes it harder to write documentation in the code since you
need to use the proper markup commands. And depending on the tool
used for this there may be restrictions on how comments have to be
structured.
2. It makes it harder to read comments in the source code, since they
will contain all sorts of distracting markup.
3. In my experience the approach usually leads to fairly useless
documentation.
prev parent reply other threads:[~2009-10-27 7:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:14 Jan Kratochvil
2009-10-12 17:12 ` Tom Tromey
2009-10-12 17:16 ` Jan Kratochvil
2009-10-12 18:00 ` Daniel Jacobowitz
2009-10-12 18:07 ` Jan Kratochvil
2009-10-12 18:13 ` Daniel Jacobowitz
2009-10-12 18:20 ` Jan Kratochvil
2009-10-12 18:26 ` Tom Tromey
2009-10-12 18:30 ` Jan Kratochvil
2009-10-12 18:54 ` Eli Zaretskii
2009-10-12 19:10 ` Daniel Jacobowitz
2009-10-12 19:25 ` Tom Tromey
2009-10-12 20:23 ` Eli Zaretskii
2009-10-12 18:57 ` Eli Zaretskii
2009-10-13 8:23 ` Jeremy Bennett
2009-10-13 18:16 ` Eli Zaretskii
2009-10-13 19:13 ` Jan Kratochvil
2009-10-13 19:18 ` Eli Zaretskii
2009-10-27 10:07 ` Mark Kettenis [this message]
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=200910270717.n9R7H58K006139@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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