public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/44015] template parameters not documented
Date: Thu, 06 May 2010 19:44:00 -0000	[thread overview]
Message-ID: <20100506194440.7293.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44015-19136@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from redi at gcc dot gnu dot org  2010-05-06 19:44 -------
basic_stringstream etc. are missing docs for their default template arguments
too, I think it's because the doxygen comments are on the class template
definitions, not on the forward declarations in <iosfwd> and
<bits/stringfwd.h>, and the default parameters are only defined in the forward
declarations.

For types, such as vector, with no forward declaration the default template
args are documented by doxygen


-- 

redi at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |documentation


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


  parent reply	other threads:[~2010-05-06 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 17:36 [Bug libstdc++/44015] New: " giecrilj at stegny dot 2a dot pl
2010-05-06 17:39 ` [Bug libstdc++/44015] " paolo dot carlini at oracle dot com
2010-05-06 19:44 ` redi at gcc dot gnu dot org [this message]
     [not found] <bug-44015-4@http.gcc.gnu.org/bugzilla/>
2012-05-02 22:26 ` bkoz at gcc dot gnu.org
2012-05-02 22:42 ` bkoz at gcc dot gnu.org
2013-03-22 14:43 ` jakub at gcc dot gnu.org
2013-05-31 10:57 ` jakub at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2015-06-22 14:26 ` rguenth at gcc dot gnu.org
2023-05-16 19:41 ` pinskia at gcc dot gnu.org

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=20100506194440.7293.qmail@sourceware.org \
    --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).