Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: stanshebs@earthlink.net
Cc: eliz@gnu.org, dje@google.com, gdb@sourceware.org
Subject: Re: A new strategy for internals documentation
Date: Fri, 09 Aug 2013 09:53:00 -0000	[thread overview]
Message-ID: <201308090949.r799nMLL024338@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <520423A2.6010304@earthlink.net> (message from Stan Shebs on Thu,	08 Aug 2013 16:02:58 -0700)

> Date: Thu, 08 Aug 2013 16:02:58 -0700
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> 3. Introduce an annotation/structured scheme in source code comments.
> 
> You're skeptical, but not opposed to this, right?

It's not going to make the source code comments more readable.  Will
probably make people focus on getting the sybtax of the annotations
right instead of the actual context.

> 4. Use Doxygen.
> 
> Are you for or against, or indifferent?
> 
> (For me Doxygen gets the nod by elimination, if nothing else.  In the
> rather lengthy
> 
> http://en.wikipedia.org/wiki/Comparison_of_documentation_generators
> 
> there are not a lot of options that are portable, GPL, etc.  LLVM's use
> of Doxygen, http://llvm.org/doxygen/index.html , seems pretty useful.)

Yeah, that's a typical example of doxygen-generated documentation.
Lots of function prototypes, a few inheritance diagrams, and barely
any actual content.  Not my defenition of useful.  In fact I'm pretty
much conditioned such that my response to seeing doxygen generated
pages is to not ever bother reading it.

Stan, I fear you're proposing a technical solution for a social
probleem.


  parent reply	other threads:[~2013-08-09  9:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 22:26 Stan Shebs
2013-08-07  4:28 ` Eli Zaretskii
2013-08-07 19:58   ` Stan Shebs
2013-08-08 17:28     ` Eli Zaretskii
2013-08-08 21:08       ` Doug Evans
2013-08-08 21:56         ` Eli Zaretskii
2013-08-08 23:03           ` Stan Shebs
2013-08-09  8:08             ` John Gilmore
2013-08-09  9:53               ` Eli Zaretskii
2013-08-09  9:35             ` Eli Zaretskii
2013-08-09 23:04               ` Stan Shebs
2013-08-09  9:53             ` Mark Kettenis [this message]
2013-08-09 23:28               ` Stan Shebs
2013-08-08 23:04           ` Doug Evans
2013-08-09  9:13             ` Eli Zaretskii
2013-08-10  1:13             ` Yao Qi
2013-08-21 18:09     ` Steinar Bang
2013-08-21 20:02       ` Eli Zaretskii
2013-08-22 18:29         ` Steinar Bang
2013-08-08  3:45   ` Yao Qi
2013-08-08 17:31     ` Eli Zaretskii
2013-08-09  1:30       ` John Gilmore
2013-08-09  9:26         ` Eli Zaretskii
2013-08-09 18:16           ` Tom Tromey
2013-08-09 18:36             ` Eli Zaretskii
2013-08-09 22:31         ` Stan Shebs
2013-08-09 23:32           ` Matt Rice
2013-08-10  2:24           ` John Gilmore
2013-08-08 20:43   ` Tom Tromey
2013-08-08 20:57   ` Doug Evans
2013-08-08 20:41 ` Tom Tromey

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=201308090949.r799nMLL024338@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb@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