public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58729] tr2::dynamic_bitset::resize fails
Date: Wed, 16 Oct 2013 11:49:00 -0000	[thread overview]
Message-ID: <bug-58729-4-qtMzMU5NAc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58729-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Comment on attachment 31017
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31017
Patch dynamic_bitset...

The new dynamic_bitset.tcc file should have a different doxygen block from the
main header:

+/** @file tr2/dynamic_bitset
+ *  This is a TR2 C++ Library header.
+ */

I suggest:

/** @file tr2/dynamic_bitset.tcc
 *  This is an internal header file, included by other library headers.
 *  Do not attempt to use it directly. @headername{tr2/dynamic_bitset}


  parent reply	other threads:[~2013-10-16 11:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 21:01 [Bug libstdc++/58729] New: " kwbent at uab dot edu
2013-10-14 21:04 ` [Bug libstdc++/58729] " kwbent at uab dot edu
2013-10-14 21:05 ` kwbent at uab dot edu
2013-10-14 21:09 ` kwbent at uab dot edu
2013-10-14 21:14 ` paolo.carlini at oracle dot com
2013-10-15  0:48 ` 3dw4rd at verizon dot net
2013-10-16 11:31 ` 3dw4rd at verizon dot net
2013-10-16 11:49 ` redi at gcc dot gnu.org [this message]
2013-10-16 11:57 ` paolo.carlini at oracle dot com
2013-10-16 12:33 ` redi at gcc dot gnu.org
2013-10-16 12:53 ` 3dw4rd at verizon dot net
2013-10-16 13:08 ` paolo.carlini at oracle dot com
2013-10-16 13:24 ` paolo.carlini at oracle dot com
2013-10-19  1:31 ` emsr at gcc dot gnu.org
2013-10-19 21:35 ` 3dw4rd at verizon dot net
2013-10-21 13:52 ` emsr at gcc dot gnu.org
2013-10-21 13:57 ` paolo.carlini at oracle dot com
2013-10-26 16:13 ` redi 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=bug-58729-4-qtMzMU5NAc@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).