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++/40380] class documentation should mention include file to use Date: Thu, 27 Apr 2023 16:00:55 +0000 [thread overview] Message-ID: <bug-40380-4-BQ8BvVjbUd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40380-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40380 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- Grr, I've just noticed that classes defined in a header with no file extension do not get an implicit @headerfile, the way that classes defined in a foo.h header do. See https://github.com/doxygen/doxygen/issues/10010 This is frustrating for libstdc++, because **none** of the public headers have an extension, so we can't rely on all the contents of e.g. <memory_resource> getting a correct #include <memory_resource> displayed. The _only_ classes which show a #include are the ones in a .h file where it's always wrong (until we add an explicit @headerfile to them). So unless that doxygen issue gets fixed, we need an explicit @headerfile on every single class in the library. Sigh.
next prev parent reply other threads:[~2023-04-27 16:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40380-4@http.gcc.gnu.org/bugzilla/> 2012-05-02 22:58 ` bkoz at gcc dot gnu.org 2021-07-01 20:11 ` redi at gcc dot gnu.org 2021-07-21 18:52 ` redi at gcc dot gnu.org 2023-04-27 10:29 ` cvs-commit at gcc dot gnu.org 2023-04-27 10:42 ` redi at gcc dot gnu.org 2023-04-27 16:00 ` redi at gcc dot gnu.org [this message] 2023-04-28 13:10 ` cvs-commit at gcc dot gnu.org 2023-05-16 19:41 ` pinskia at gcc dot gnu.org 2024-03-18 14:08 ` cvs-commit at gcc dot gnu.org 2009-06-08 21:36 [Bug libstdc++/40380] New: " tromey at gcc dot gnu dot org 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-4-BQ8BvVjbUd@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).