Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Doxygenate gdbtypes.h
Date: Tue, 04 Mar 2014 17:36:00 -0000	[thread overview]
Message-ID: <8761ntoogy.fsf@gnu.org> (raw)
In-Reply-To: <531529D4.3050309@earthlink.net>

Stan Shebs <stanshebs@earthlink.net> skribis:

> Give the histrionics a rest, please.  You claimed it was against policy,
> but then you never replied when I asked what specific policy
> is being violated.

Just because some GNU packages use Doxygen (or CMake, or...) doesn’t
mean it’s a good idea; and it remains a GCS violation.

> Two extra characters per comment block is not a "lot of random
> garbage" or "vandalism" - over-the-top statements like that are not
> going to convince anybody of anything.

GNU has a history of well-written documentation and well-commented code.
The rationale is documented, and IMO still holds.

As a GNU user and hacker, I’ve long appreciated GNU’s luxurious approach.
In contrast, I view the approach that Doxygen, Javadoc & co. favor as an
insult to the reader.

So I can sympathize with Mark’s comment.

Thanks,
Ludo’.


  reply	other threads:[~2014-03-04 17:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  0:16 Stan Shebs
2014-03-04  0:39 ` Mark Kettenis
2014-03-04  1:18   ` Stan Shebs
2014-03-04 17:36     ` Ludovic Courtès [this message]
2014-03-04 18:18       ` Joel Brobecker
2014-03-04 19:03       ` Stan Shebs
2014-03-04 19:15         ` Eli Zaretskii
2014-03-04 19:51           ` Stan Shebs
2014-03-05  1:17             ` Rob Savoye
2014-03-13  2:38 ` 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=8761ntoogy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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