public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giecrilj at stegny dot 2a.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/50143] Doxygen API documentation is invalid
Date: Sun, 21 Aug 2011 19:35:00 -0000	[thread overview]
Message-ID: <bug-50143-4-ENIeValJI3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50143-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143

--- Comment #2 from Christopher Yeleighton <giecrilj at stegny dot 2a.pl> 2011-08-21 19:33:07 UTC ---
Please tell me if you find the following argument invalid:

  1. 
It is the responsibility of the library to provide API documentation for the
developers using the library.

  2. 
The library can provide the documentation in whatever way it seems fit,
provided that the documentation is readable and meets its essential purpose.

  3.
The library documentation provided with the library is unreadable.

Conclusion: the library failed to provide appropriate documentation.  Ergo, it
is the library‘s fault.  

The user is not interested in what particular tool the library manufacturer
internally uses, as long as it works.  The user is not in position to tell
whether the fault is in Doxygen markup or in Doxygen engine; in either case,
the user is not in position to fix the documentation so as to make it useful.

If you feel that this is Doxygen‘s fault, you, as the manufacturer, have the
following options:

  * 
Diagnose the problem, file a bug at Doxygen and hope it will get fixed.

  * 
Use some other tool to generate API documentation.

  * 
Do nothing, and continue to ship a broken product pretending it is not your
fault.

The choice is yours.  

I would be happy to be able to reproduce this Doxygen problem and isolate a
reportable test case; however, I am not sure I know how to do it.  It seems
building gcc first is necessary, and it is quite a job.


  parent reply	other threads:[~2011-08-21 19:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21 15:04 [Bug libstdc++/50143] New: " giecrilj at stegny dot 2a.pl
2011-08-21 15:13 ` [Bug libstdc++/50143] " paolo.carlini at oracle dot com
2011-08-21 19:35 ` giecrilj at stegny dot 2a.pl [this message]
2011-08-21 20:07 ` redi at gcc dot gnu.org
2011-08-21 20:21 ` paolo.carlini at oracle dot com
2011-08-21 20:45 ` giecrilj at stegny dot 2a.pl
2011-08-21 20:46 ` giecrilj at stegny dot 2a.pl
2011-08-21 20:50 ` giecrilj at stegny dot 2a.pl
2011-08-21 20:54 ` paolo.carlini at oracle dot com
2011-08-21 20:56 ` giecrilj at stegny dot 2a.pl
2011-08-21 21:00 ` dominiq at lps dot ens.fr
2011-08-21 21:04 ` paolo.carlini at oracle dot com
2011-08-21 21:05 ` paolo.carlini at oracle dot com
2011-08-21 21:11 ` giecrilj at stegny dot 2a.pl
2011-08-21 21:48 ` redi at gcc dot gnu.org
2011-08-21 22:06 ` paolo.carlini at oracle dot com
2011-08-22 13:39 ` joseph at codesourcery dot com
2011-08-22 14:39 ` redi at gcc dot gnu.org
2011-08-22 14:49 ` redi at gcc dot gnu.org
2011-08-22 19:05 ` giecrilj at stegny dot 2a.pl
2011-08-22 19:07 ` giecrilj at stegny dot 2a.pl
2011-08-22 19:15 ` redi at gcc dot gnu.org
2011-08-30 13:26 ` giecrilj at stegny dot 2a.pl
2011-08-30 13:27 ` redi at gcc dot gnu.org
2011-08-30 13:30 ` redi at gcc dot gnu.org
2011-08-30 14:07 ` giecrilj at stegny dot 2a.pl

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=bug-50143-4-ENIeValJI3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).