public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/40380] New: class documentation should mention include file to use Date: Mon, 08 Jun 2009 21:36:00 -0000 [thread overview] Message-ID: <bug-40380-360@http.gcc.gnu.org/bugzilla/> (raw) I was reading the documentation for unique_ptr: http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/a00587.html This mentions unique_ptr.h -- but that is not a user-allowed header file. Instead the user ought to write "#include <memory>". This is not mentioned anywhere, but IMO it should be. -- Summary: class documentation should mention include file to use Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tromey at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40380
next reply other threads:[~2009-06-08 21:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-08 21:36 tromey at gcc dot gnu dot org [this message] 2009-06-18 0:00 ` [Bug libstdc++/40380] " bkoz at gcc dot gnu dot org 2009-06-18 0:34 ` bkoz at gcc dot gnu dot 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-40380-360@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: linkBe 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).